Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-device-farm-runner 0.0.5 #1073

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
157 changes: 157 additions & 0 deletions steps/aws-device-farm-runner/0.0.5/step.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,157 @@
title: Amazon Device Farm Runner
summary: Amazon Device Farm Runner
description: Deploys app to device farm and starts a test run. [Please see the wiki
for setup instructions](https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/wiki).
website: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner
source_code_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner
support_url: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues
published_at: 2017-06-21T09:19:56.224790211-07:00
source:
git: https://github.com/peartherapeutics/bitrise-aws-device-farm-runner.git
commit: 8e6dc423971abd4f8784505e241f09d47e4830a4
host_os_tags:
- linux
- osx-10.9
- osx-10.10
type_tags:
- test
deps:
brew:
- name: awscli
bin_name: aws
- name: jq
bin_name: jq
apt_get:
- name: awscli
bin_name: aws
- name: jq
bin_name: jq
is_requires_admin_user: false
is_always_run: false
is_skippable: false
run_if: ""
inputs:
- access_key_id: $AWS_ACCESS_KEY
opts:
description: Access key for your AWS/IAM user. Define this as a secret environment
variable in your workflow.
is_required: true
summary: ""
title: AWS Access Key
- opts:
description: Secret key for your AWS/IAM user. Define this as a secret environment
variable in your workflow.
is_required: true
summary: ""
title: AWS Secret Key
secret_access_key: $AWS_SECRET_KEY
- device_farm_project: ""
opts:
description: Project ARNs can be obtained using the AWS CLI `devicefarm list-projects`
command.
is_required: true
summary: ""
title: Device Farm Project ARN
- billing_method: METERED
opts:
description: This step specifies the billing methodfor your test run. Use `METERED`
for free tier and pay-as-you-go billing, and `UNMETERED` to use [pre-paid device
slots](https://docs.aws.amazon.com/devicefarm/latest/developerguide/how-to-purchase-device-slots.html).
is_required: false
summary: ""
title: Billing Method
value_options:
- METERED
- UNMETERED
- opts:
description: |-
Filename of test package to run.
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.
The most recently uploaded package with this name will be used.
is_required: true
summary: ""
title: Test Package Filename
test_package_name: ""
- opts:
description: '[See the Test.type documentation](http://docs.aws.amazon.com/devicefarm/latest/APIReference/API_Test.html#devicefarm-Type-Test-type).'
is_required: true
summary: ""
title: Test Type
test_type: ""
- opts:
description: ""
is_required: true
summary: ""
title: Platform
value_options:
- ios
- android
- ios+android
platform: ios+android
- ipa_path: $BITRISE_IPA_PATH
opts:
description: Required for iOS runs.
title: IPA file path
- ios_pool: ""
opts:
description: Required for iOS runs. ARNs can be obtained using the AWS CLI `devicefarm
list-device-pools` command.
title: Device Farm iOS Device Pool ARN
- apk_path: $BITRISE_SIGNED_APK_PATH
opts:
description: Required for Android runs.
title: APK file path
- android_pool: ""
opts:
description: Required for Android runs. ARNs can be obtained using the AWS CLI
`devicefarm list-device-pools` command.
title: Device Farm Android Device Pool ARN
- opts:
description: |
If you want to specify a name, this prefix will be used
followed by platform and bitrise build number.
summary: ""
title: Run Name Prefix
run_name_prefix: ""
- build_version: $BITRISE_BUILD_NUMBER
opts:
description: Build number
is_required: true
title: Build Number
- aws_region: $AWS_REGION
opts:
description: |
If you want to specify a different AWS region. Leave
empty to use the default config/env setting.
summary: ""
title: AWS Region
- opts:
description: |-
If set to true, the script waits for the test run to complete on
Device farm before returning success/failure. This will slow down your
Bitrise runs, however allows you to make decisions in subsequent steps
based on success/failure of the tests.
title: Whether or not to wait for the test results from device farm
value_options:
- "true"
- "false"
run_wait_for_results: "true"
- opts:
description: |-
Depending on your tests, you may or may not wish to fail the step if
Device farm returns a WARNED result. Only takes effect if
`run_wait_for_results` is also enabled.
title: Fail if the device farm results return result of WARNED
value_options:
- "true"
- "false"
run_fail_on_warning: "true"
outputs:
- BITRISE_DEVICEFARM_RESULTS_RAW: null
opts:
description: This is the full results of the run in JSON from AWS Device Farm
title: The full output from the device farm run
- BITRISE_DEVICEFARM_RESULTS_SUMMARY: null
opts:
description: A nice summary suitable for feeding into something like a slack message.
title: A human-readable summary of the results.