-
Notifications
You must be signed in to change notification settings - Fork 1
/
step.yml
101 lines (95 loc) · 3.56 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
101
#
# 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: |-
TryoutApps Shaman
summary: |
Uploads apps to Infinum's TryoutApps
description: |
Uploads apps to Infinum's TryoutApps using shaman deploy script.
Only one build at the time can be uploaded.
website: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy
source_code_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy
support_url: https://github.com/infinum/TryoutApps-Shaman-Bitrise-Deploy/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
- flutter
# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
- deploy
is_requires_admin_user: false
is_always_run: false
is_skippable: false
run_if: ""
toolkit:
bash:
entry_file: step.sh
inputs:
- shaman_token:
opts:
title: "Token used for authentication with TryoutApps"
description: |
Get your user token from https://[TENANT].tryoutapps.com/users/me
is_required: true
is_sensitive: true
- shaman_config_path: "./.shaman.yml"
opts:
title: "Path to the shaman.yml file"
description: |
By default, this value is set to './.shaman.yml'
is_required: true
- environment_name:
opts:
title: "Deploy environment name"
description: |
Name defined in shaman.yml
is_required: true
- file_path:
opts:
category: Config
title: "Path to the file that is to be uploaded"
description: |
By default, this value is read from shaman.yml file. If you need to use a custom path, you can set it here.
is_required: false
- changelog_message:
opts:
title: "Message used for setting the change log"
category: Config
description: |
A message that can be used as a changelog, you can store value from tag/commit/script in a custom global variable (e.g. "${TAG_MESSAGE}") and then use it here.
is_required: false
- release_name:
opts:
title: "Release name (ZIP platform only)"
category: Config
description: |
Release name used only if ZIP is uploaded to TryoutApps.
is_required: false
- ruby_version:
opts:
title: "Ruby version"
category: Config
description: |
When set, a specific Ruby version will be installed on the machine. Otherwise, the default version from the machine will be used.
is_required: false