/
step.yml
153 lines (142 loc) · 5.15 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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
title: "Deploy to iTunes Connect (with Deliver)"
summary: Upload the archive to iTunes Connect and you can also submit it to TestFlight Beta Testing
description: |-
Deploy to iTunes Connect, using the
fantastic [Deliver](https://github.com/KrauseFx/deliver)
Ruby gem.
**If this is the very first build** of the app
you try to deploy to iTunes Connect then you might want to upload the first
build manually to make sure it fulfills the initial iTunes Connect submission
verification process.
**Be advised** that this
step uses a well maintained, open source tool which
uses *undocumented and unsupported APIs* (because the current
iTunes Connect platform does not have a documented and supported API)
to perform the deployment.
This means that when the API changes
**this step might fail until the tool is updated**.
## Setup guide and notes
* 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.
* Requires an **App Store iOS distibution Provisioning Profile**
* 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*)
website: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver
source_code_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver
support_url: https://github.com/bitrise-io/steps-deploy-to-itunesconnect-deliver/issues
host_os_tags:
- "osx-10.10"
project_type_tags:
- ios
type_tags:
- "deploy"
is_requires_admin_user: false
is_always_run: false
is_skippable: false
dependencies: []
run_if: ""
inputs:
- ipa_path: "$BITRISE_IPA_PATH"
opts:
title: "IPA path"
summary: ""
description: |-
Path of the IPA file, to be deployed to iTunes Connect
is_required: false
- pkg_path: "$BITRISE_PKG_PATH"
opts:
title: "PKG path"
summary: ""
description: |-
Path of the PKG file, to be deployed to iTunes Connect
is_required: false
- itunescon_user: ""
opts:
title: "iTunes Connect: User Apple ID (email)"
summary: ""
description: |-
Login Apple ID (email) for the iTunes Connect site.
*Make sure that this email is verified,
your Apple ID cannot be used until you verify it
on Apple's website!*
is_required: true
- password: ""
opts:
title: "iTunes Connect: Password"
summary: ""
description: |-
Password for the specified User Apple ID.
**Note:** if your password
contains special characters
and you experience problems, please
consider changing your password
to something with only
alphanumeric characters.
is_required: true
- app_id: ""
opts:
title: "iTunes Connect: App Apple ID"
summary: ""
description: |-
The App's *Apple ID* on iTunes Connect.
Open the **App's page on iTunes Connect**,
click on **More**, click on *About this app*,
copy the *Apple ID*'s value from here (numeric, like 846814360)
is_required: true
- submit_for_beta: "no"
opts:
title: "Submit for TestFlight Beta Testing?"
summary: ""
description: |
Wait for the submission to be processed and then
enable **TestFlight Beta Testing** for this specific version?
If this option is disabled then this step won't wait
for the new version to be processed on iTunes Connect
and won't enable it for *TestFlight Beta Testing* automatically.
*Enabling this option will wait for the submission to be
processed which might take a couple of minutes after the
new version is deployed to iTunes Connect*.
**NOTE:** if this option is enabled then this step will
fail if it can't enable TestFlight Beta Testing for the
version, even if the version was successfully uploaded
to iTunes Connect and only the TestFlight Beta Testing
submission failed.
value_options: ["yes", "no"]
is_required: true
is_expand: false
- skip_metadata: "yes"
opts:
title: "Skip Metadata?"
summary: ""
description: |
Flag to skip uploading the appstore metadata.
value_options: ["yes", "no"]
is_required: true
is_expand: false
- skip_screenshots: "yes"
opts:
title: "Skip Screenshots?"
summary: ""
description: |
Flag to skip uploading changes to appstore screenshots.
value_options: ["yes", "no"]
is_required: true
is_expand: false
- team_name: ""
opts:
title: "iTunes Connect: Team name"
summary: ""
description: |-
The App's *Team Name* on iTunes Connect.
This field are required when using iTunes Connect account
linked to multiple publish team.
- update_deliver: "yes"
opts:
title: "Update deliver gem"
summary: ""
description: |-
Should the step use the latest version of `deliver` gem,
or the preinstalled one?
is_required: true
value_options:
- "yes"
- "no"
outputs: []