-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathstep.yml
More file actions
executable file
·129 lines (120 loc) · 3.62 KB
/
step.yml
File metadata and controls
executable file
·129 lines (120 loc) · 3.62 KB
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
title: Export macOS Xcode archive
summary: Export macOS Xcode archive
description: |-
This step exports an app (`.app` or `.pkg` from an existing macOS `xcarchive`. This is useful when one archive needs to be exported with different distribution methods without rebuilding the archive.
website: https://github.com/bitrise-steplib/steps-export-xcarchive-mac
source_code_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac
support_url: https://github.com/bitrise-steplib/steps-export-xcarchive-mac/issues
host_os_tags:
- osx-10.10
project_type_tags:
- macos
- xamarin
type_tags:
- utility
is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ""
toolkit:
go:
package_name: github.com/bitrise-steplib/steps-export-xcarchive-mac
inputs:
- archive_path: $BITRISE_MACOS_XCARCHIVE_PATH
opts:
title: macOS archive path
description: |-
Path to the macOS archive (.xcarchive) which should be exported.
- export_method: development
opts:
title: Select method for export
description: |-
Describes how Xcode should export the archive.
value_options:
- app-store
- development
- developer-id
- none
is_required: true
- upload_bitcode: "yes"
opts:
category: Export configuration
title: Include bitcode
description: For __App Store__ exports, should the package include bitcode?
value_options:
- "yes"
- "no"
is_required: true
- compile_bitcode: "yes"
opts:
category: Export configuration
title: Rebuild from bitcode
description: For __non-App Store__ exports, should Xcode re-compile the app from bitcode?
value_options:
- "yes"
- "no"
is_required: true
- team_id:
opts:
title: The Developer Portal team to use for this export
description: |-
The Developer Portal team to use for this export.
Format example:
- `1MZX23ABCD4`
- custom_export_options_plist_content:
opts:
title: Custom export options plist content
description: |-
Specifies a custom export options plist content that configures archive exporting.
If empty, step generates these options based on the embedded provisioning profile,
with default values.
Auto generated export options available for export methods:
- app-store
- ad-hoc
- enterprise
- development
If step doesn't find export method based on provisioning profile, development will be use.
Call `xcodebuild -help` for available export options.
- use_legacy_export: "no"
opts:
title: Use legacy export method?
description: If this input is set to `yes`, the step will use legacy export method.
value_options:
- "yes"
- "no"
is_required: true
- legacy_export_provisioning_profile_name:
opts:
title: Specify Provisioning Profile name to use by export
description: |-
If this input is empty, xcodebuild will grab one of the matching installed provisining profile.
- legacy_export_output_format: app
opts:
title: Specify export format
description: |-
Specify export format
value_options:
- app
- pkg
is_required: true
- verbose_log: "no"
opts:
title: Enable verbose logging?
description: Enable verbose logging?
is_required: true
value_options:
- "yes"
- "no"
outputs:
- BITRISE_APP_PATH:
opts:
title: macOS .app path
description: The created macOS `.app` file's path
- BITRISE_PKG_PATH:
opts:
title: macOS .pkg path
description: The created macOS `.pkg` file's path
- BITRISE_IDEDISTRIBUTION_LOGS_PATH:
opts:
title: "`xcdistributionlogs` ZIP path"
description: Path to the `xcdistributionlogs` ZIP file