actions-marketplace-validations/fredybp/Xcodebuild

A continuously resilient `xcodebuild` action. “The best `xcodebuild` action by far.” ―mxcl

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
Runtime
Deprecated runtime
namedescriptionrequireddefault
xcodeA semantic version range, eg. ^10, ~10.3 or 10.3.1 Leave unset for the image‑default. no
swiftA semantic version range, eg. ^5, ~5.4 or 5.4.1no
platformEither `iOS`, `tvOS`, `macOS`, `watchOS` or (more rarely) `mac-catalyst` Leave unset and `xcodebuild` decides itself. no
action* The most common actions are `test`, `build`. * See the `xcodebuild` manual for available actions. * Specifying `none` skips the explicit `xcodebuild` step allowing you to use this (GitHub) Action solely for selecting an Xcode version. * Specifying `''`, `null` or `~` will cause xcodebuild to behave as it does without an action specified (usually `build`) notest
code-coverageEnables code coveragenofalse
authentication-key-base64A Base64-encoded authentication key issued by App Store Connect. If specified, `xcodebuild`` will authenticate with the Apple Developer website using this credential. The `authentication-key-id` and `authentication-key-issuer-id` parameters are required. Using this key, `xcodebuild` will register the GitHub Actions runner device and manage code signing certificates for it. Please note that this may cause undesired behavior when using GitHub-hosted runners. For best results, use App Store Connect API keys only on self-hosted runners. no
authentication-key-idThe key identifier associated with the App Store Conect authentication key specified in `authentication-key-base64`. This string can be located in the users and access details for your provider at "https://appstoreconnect.apple.com". For best results, use App Store Connect API keys only on self-hosted runners. no
authentication-key-issuer-idThe App Store Connect issuer identifier associated with the authentication key specified in `authentication-key-base64`. This string can be located in the users and access details for your provider at "https://appstoreconnect.apple.com". For best results, use App Store Connect API keys only on self-hosted runners. no
code-sign-certificateA Base64-encoded certificate to be installed to the macOS Keychain for code signing. It is removed from the keychain in the post action. This certificate should correspond to the `CODE_SIGN_IDENTITY` specified in your project or to the `code-sign-identity` input. Pass this in as a GitHub Encrypted Secret. Requires macOS and `code-sign-certificate-passphrase`. no
code-sign-certificate-passphraseThe passphrase used to protect the code signing certificate. Pass this in as a GitHub Encrypted Secret. no
code-sign-identityIdentity to be used for code signing. If your project specifies a `CODE_SIGN_IDENTITY`, this will override it. no
mobile-provisioning-profiles-base64A multiline list of Base64-encoded mobile provisioning profiles. no
provisioning-profiles-base64A multiline list of Base64-encoded Mac provisioning profiles. no
working-directoryno
configurationTypically `Release` or `Debug`. Leave unset and `xcodebuild` decides itself. no
schemeA scheme defined by an Xcode project or workspace. If not specified, xcodebuild builds only the first target. no
warnings-as-errorsFails the build if any warnings in *non test targets*.nofalse
verbosityOne of `xcpretty`, `quiet` or `verbose`.noxcpretty
upload-logsOne of `always` or `on-failure`. Consider `always` if you want access to your coverage-reports. Beware that artifacts count against your GitHub Actions storage limits. noon-failure
use-generate-xcodeprojUses `swift package generate-xcodeproj` to generate `.xcproject` file (will be debrecated as Xcode can build from a `Package.swift`). nofalse

no outputs