Skip to content

Commit

Permalink
Adding build inputs (#2585)
Browse files Browse the repository at this point in the history
* Adding build inputs

* Update yaml-getting-started.md

* Update yaml-getting-started.md

* Update yaml-getting-started.md

* Update yaml-getting-started.md
  • Loading branch information
icarusdust authored Jun 10, 2024
1 parent 9b05f94 commit 385844c
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions content/yaml-basic-configuration/yaml-getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,10 @@ workflows:
- ${TENANT_NAME}
instance_type: mac_mini_m1
max_build_duration: 60
inputs: # more information about build inputs:https://docs.codemagic.io/knowledge-codemagic/build-inputs/
name: # input ID
description: Input description
default: Codemagic
environment:
groups:
- group_name
Expand All @@ -139,6 +143,7 @@ workflows:
source: true
cancel_previous_builds: false
scripts:
- echo "Hello, ${{ inputs.name }}"
- ...
artifacts:
- build/**/outputs/bundle/**/*.aab
Expand Down Expand Up @@ -185,6 +190,10 @@ The main sections in each workflow are described below.
**Note:** The `linux_x2` and `windows_x2` are only available for teams and users with [billing enabled](../billing/billing/). `mac_mini_m2` is only available on fixed price annual plan.
{{</notebox>}}

### Build inputs

Build inputs are parameters that allow you to customize your build configurations right before starting a new build without hardcoding them in **codemagic.yaml**. For example, build inputs can be used to determine whether to build the workflow for test or release purposes or which Xcode version to use, etc. More information about how to configure build inputs and examples can be found [here](https://docs.codemagic.io/knowledge-codemagic/build-inputs/]).

### Environment

`environment:` section specifies the environment variables and their respective group and build machine software versions.
Expand Down

0 comments on commit 385844c

Please sign in to comment.