This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
forked from tamasbazs/steps-ios-auto-provision
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstep.yml
201 lines (173 loc) · 6.97 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
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
title: iOS Auto Provision
summary: Automatically manages your iOS Provisioning Profiles for your Xcode project
description: |-
### Automatically manages your iOS Provisioning Profiles for your Xcode project.
__Setup guide__: [Managing iOS code signing files - automatic provisioning](https://devcenter.bitrise.io/code-signing/ios-code-signing/ios-auto-provisioning/)
In the case of __Xcode managed codesigning__ projects:
- downloads the __Xcode managed Provisioning Profiles__ and installs them for the build
- installs the provided __Codesigning Certificates__ into the Keychain
In the case of __Manual codesigning__ projects:
- ensures that the __Application Identifier__ exists on the Apple Developer Portal
- ensures that the __project's Capabilities__ are set correctly in the Application Identifier
- ensures that the __Provisioning Profiles__ exist on the Apple Developer Portal and are installed for the build
- ensure that all the available __Test Devices__ exist on the Apple Developer Portal and are included in the Provisioning Profiles
- installs the provided __Codesigning Certificates__ into the Keychain
website: https://github.com/bitrise-steplib/steps-ios-auto-provision
source_code_url: https://github.com/bitrise-steplib/steps-ios-auto-provision
support_url: https://github.com/bitrise-steplib/steps-ios-auto-provision/issues
host_os_tags:
- osx-10.10
- ubuntu-16.04
project_type_tags:
- ios
type_tags:
- code-sign
is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ".IsCI"
inputs:
- distribution_type: development
opts:
title: Distribution type
description: Describes how Xcode should sign your project.
value_options:
- "development"
- "app-store"
- "ad-hoc"
- "enterprise"
is_required: true
- team_id:
opts:
title: The Developer Portal team id
description: |-
The Developer Portal team to manage the project's code signing files.
__If your Developer Portal Account belongs to multiple development team, this input is required!__
Otherwise specify this input if you want to manage the Provisioning Profiles with a different team than the one set in your project.
If you leave it empty the team defined by the project will be used.
__Example:__ `1MZX23ABCD4`
- project_path: $BITRISE_PROJECT_PATH
opts:
title: Xcode Project (or Workspace) path
description: A `.xcodeproj` or `.xcworkspace` path.
is_required: true
- scheme: $BITRISE_SCHEME
opts:
title: Scheme name
description: The Xcode Scheme to use.
is_required: true
- configuration:
opts:
title: Configuration name
description: |-
The Xcode Configuration to use.
By default your Scheme defines which Configuration (Debug, Release, ...) should be used,
but you can overwrite it with this option.
- generate_profiles: "no"
opts:
title: Should the step try to generate Provisioning Profiles even if Xcode managed signing is enabled in the Xcode project?
description: |-
In the case of __Xcode managed code signing__ projects, by default the step downloads and installs the Xcode managed Provisioning Profiles.
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__),
the step will fall back to use the Xcode managed Provisioning Profiles if there is an issue.
__This input has no effect in the case of Manual codesigning projects.__
value_options:
- "yes"
- "no"
- verbose_log: "no"
opts:
category: Debug
title: Enable verbose logging?
description: Enable verbose logging?
is_required: true
value_options:
- "yes"
- "no"
- certificate_urls: $BITRISE_CERTIFICATE_URL
opts:
category: Debug
title: Certificate URL
description: |
URLs of the certificates to download.
Multiple URLs can be specified, separated by a pipe (`|`) character,
you can specify a local path as well, using the `file://` scheme.
__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.
__Example:__ `file://./development/certificate/path|https://distribution/certificate/url`
is_required: true
is_sensitive: true
- passphrases: $BITRISE_CERTIFICATE_PASSPHRASE
opts:
category: Debug
title: Certificate passphrase
description: |
Certificate passphrases.
Multiple passphrases can be specified, separated by a pipe (`|`) character.
__Specified certificate passphrase count should match the count of the certificate urls.__
__Example__ (1 certificate with empty passphrase, 1 certificate with non-empty passphrase): `|distribution-passphrase`
is_required: true
is_sensitive: true
- keychain_path: $HOME/Library/Keychains/login.keychain
opts:
category: Debug
title: Keychain path
description: The Keychain path.
is_required: true
- keychain_password: $BITRISE_KEYCHAIN_PASSWORD
opts:
category: Debug
title: Keychain's password
description: The Keychain's password.
is_required: true
is_sensitive: true
- build_url: $BITRISE_BUILD_URL
opts:
category: Debug
title: Bitrise build url
description: Bitrise build url.
is_required: true
- build_api_token: $BITRISE_BUILD_API_TOKEN
opts:
category: Debug
title: Bitrise build api token
description: Bitrise build api token.
is_required: true
is_sensitive: true
outputs:
- BITRISE_EXPORT_METHOD:
opts:
title: "The selected distribution type"
description: |-
The selected distribution type.
One of: `development`, `app-store`, `ad-hoc` or `enterprise`
- BITRISE_DEVELOPER_TEAM:
opts:
title: "The development team's ID"
description: |-
The development team's ID.
Example: `1MZX23ABCD4`
- BITRISE_DEVELOPMENT_CODESIGN_IDENTITY:
opts:
title: "The development codesign identity's name"
description: |-
The development codesign identity's name.
Example: `iPhone Developer: Bitrise Bot (VV2J4SV8V4)`
- BITRISE_PRODUCTION_CODESIGN_IDENTITY:
opts:
title: "The production codesign identity's name"
opts:
title: "The production codesign identity's name"
description: |-
The production codesign identity's name.
Example: `iPhone Distribution: Bitrise Bot (VV2J4SV8V4)`
- BITRISE_DEVELOPMENT_PROFILE:
opts:
title: "The main target's development provisioning profile's UUID"
description: |-
The main target's development provisioning profile's UUID.
Example: `c5be4123-1234-4f9d-9843-0d9be985a068`
- BITRISE_PRODUCTION_PROFILE:
opts:
title: "The main target's production provisioning profile's UUID"
description: |-
The main target's production provisioning profile's UUID.
Example: `c5be4123-1234-4f9d-9843-0d9be985a068`