actions-marketplace-validations/Xcodebuild Action

Runs xcodebuild e.g. to run tests.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stalelast commit Oct 31, 2022
License
Apache 2.0
Runtime
Deprecated runtime

Pinned Snippet

workflow.ymlSHA-pinned
uses: actions-marketplace-validations/sersoft-gmbh_xcodebuild-action@74fa5c0560a17e3f7db658ea593603ca0ea324e8 # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
workspaceThe path to the xcworkspace to build. Mutually exclusive with `project` and `spm-package`. See also `xcodebuild`'s `-workspace`.no
projectThe path to the xcodeproj to build. Mutually exclusive with `workspace` and `spm-package`. See also `xcodebuild`'s `-project`.no
spm-packageThe path to the SPM package (folder containing Package.swift) to build. Mutually exclusive with `workspace` and `project`.no
schemeThe scheme to build. Required when using a workspace. See also `xcodebuild`'s `-scheme`.no
targetThe target to build. See also `xcodebuild`'s `-target`.no
destinationThe destination specifier to build. See also `xcodebuild`'s `-destination`.no
configurationThe configuration to build. See also `xcodebuild`'s `-configuration`.no
sdkThe SDK to use for building. See also `xcodebuild`'s `-sdk`.no
archThe architecture to use for building. See also `xcodebuild`'s `-arch`.no
xcconfigThe path to an xcconfig file with build settings overrides. See also `xcodebuild`'s `-xcconfig`.no
jobsThe number of jobs to use for building. See also `xcodebuild`'s `-jobs`.no
parallelize-targetsIf `true`, the targets will be built in parallel. See also `xcodebuild`'s `-parallelizeTargets`.no
enable-code-coverageIf `true`, code coverage is enabled while testing. See also `xcodebuild`'s `-enableCodeCoverage`.no
parallel-testing-enabledIf `true`, tests are executed in parallel. See also `xcodebuild`'s `-parallel-testing-enabled`.no
maximum-concurrent-test-device-destinationsThe maximum number of device destinations to run in parallel. See also `xcodebuild`'s `-maximum-concurrent-test-device-destinations`.no
maximum-concurrent-test-simulator-destinationsThe maximum number of simulator destinations to run in parallel. See also `xcodebuild`'s `-maximum-concurrent-test-simulator-destinations`.no
quietIf `true`, xcodebuild won't print anything except warnings and errors. See also `xcodebuild`'s `-quiet`.no
hide-shell-script-environmentIf `true`, xcodebuild won't print the environment for shell build scripts. See also `xcodebuild`'s `-hideShellScriptEnvironment`.no
enable-address-sanitizerWhether the address sanitizer should be enabled. See also `xcodebuild`'s `-enableAddressSanitizer`.no
enable-thread-sanitizerWhether the thread sanitizer should be enabled. See also `xcodebuild`'s `-enableThreadSanitizer`.no
enable-undefined-behavior-sanitizerWhether the undefined behavior sanitizer should be enabled. See also `xcodebuild`'s `-enableUndefinedBehaviorSanitizer`.no
result-bundle-pathThe path that should be used for the result bundle. See also `xcodebuild`'s `-resultBundlePath`.no
result-bundle-versionThe version that should be used for the result bundle. See also `xcodebuild`'s `-resultBundleVersion`.no
cloned-source-packages-pathThe path that should be used for the cloning of remote packages. See also `xcodebuild`'s `-clonedSourcePackagesDirPath`.no
derived-data-pathThe path that should be used for derived data. See also `xcodebuild`'s `-derivedDataPath`.no
xcrootThe path to a .xcroot to use for building and/or testing. See also `xcodebuild`'s `-xcroot`.no
xctestrunThe path to a test run specification. See also `xcodebuild`'s `-xctestrun`.no
test-planThe name of the test plan associated with the scheme to use for testing. See also `xcodebuild`'s `-testPlan`.no
only-testingA (line-separated) list of tests to run. See also `xcodebuild`'s `-only-testing`.no
skip-testingA (line-separated) list of tests to skip. See also `xcodebuild`'s `-skip-testing`.no
skip-unavailable-actionsWhether unavailable actions should be skipped instead of failing the execution. See also `xcodebuild`'s `-skipUnavailableActions`.no
allow-provisioning-updatesWhether provisioning updates are allowed. See also `xcodebuild`'s `-allowProvisioningUpdates`.no
allow-provisioning-device-registrationWhether provisioning device registrations are allowed. See also `xcodebuild`'s `-allowProvisioningDeviceRegistration`.no
build-settingsArbitrary, space separated build settings (e.g. PLATFORM_NAME=iphonesimulator).no
actionThe action to perform (e.g. build, test, ...). Can also contain multiple actions.yestest
use-xcprettyWhether the output of xcodebuild should be forwarded to xcpretty.yestrue
xcpretty-colored-outputWhether xcpretty should use colored output (e.g. `xcpretty --color`).yestrue
dry-run<TEST ONLY> Whether the commands should only be composed and not actually run. Only used in test.no
namedescription
unprocessed-commandThe unprocessed command from which the executed command was resolved. E.g. paths are not resolved in this one.
executed-commandThe command that was executed.