-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstep.yml
100 lines (88 loc) · 3.42 KB
/
step.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/
title: |-
Upload to MoQuality
summary: |
Uploads an APK file to MoQuality
description: |
This step logs into your MoQuality account and uploads an APK file to MoQuality. Upon upload, a new version of your app is created with the given APK file.
website: https://github.com/moquality/bitrise-step-upload-to-moquality
source_code_url: https://github.com/moquality/bitrise-step-upload-to-moquality
support_url: https://github.com/moquality/bitrise-step-upload-to-moquality/issues
host_os_tags:
- osx-10.10
- ubuntu-16.04
# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
project_type_tags:
- ios
# - macos
- android
# - xamarin
# - react-native
# - cordova
# - ionic
# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
- test
is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ""
deps:
brew:
- name: git
- name: wget
- name: moquality/brew/mq
apt_get:
- name: git
- name: wget
toolkit:
bash:
entry_file: step.sh
inputs:
- API_KEY:
opts:
title: "API key"
summary: A MoQuality user or team's API key
description: |
This key is necessary to log in to MoQuality and upload the app.
It can be found on `Personal Profile` tab on the account page of the [MoQuality website](https://app.moquality.com/account/).
is_expand: true
is_required: true
value_options: []
- APK_PATH: "$BITRISE_APK_APTH"
opts:
title: "Path to APK file"
summary: The path to an app's APK file.
description: |
This path is necessary to determine the location of the app to be uploaded to MoQuality.
This path is often generated as an output value of a build step.
is_expand: true
is_required: false
value_options: [$BITRISE_APK_PATH]
- APP_ID:
opts:
title: "MoQuality app Id"
summary: The identifier for a MoQuality app
description: |
The MoQuality app Id is necessary to determine which app you are uploading.
You can find the app Id by [installing the MQ CLI](http://docs.moquality.com/integration-ci-cd/mq-cli/), running `mq login`, and then running `mq apps` to view your list of apps with their respective app Ids.
is_expand: true
is_required: true
value_options: []