Setting the stack for your builds

Abstract

The build stack indicates the virtual machine version that Bitrise will use to run your build. You can set the stack for all your builds, or you can set Workflow-specific stacks, either in the Workflow Editor or in the bitrise.yml file.

The build stack indicates the virtual machine version that we will use to run your build. You can set the stack for all your builds, or you can set Workflow-specific stacks.

Changing machine types using the API

You can also change build machine types for all apps owned by a single user or Workspace using the API: Changing machine types in all apps at the same time.

Setting the stack in the Workflow Editor

The simplest way to configure the build stack is in the Workflow Editor. You can set both the default stack and Workflow-specific stacks.

Setting the default stack

The default stack of your app is the stack that is used if you haven't set a specific stack for a Workflow.

Project type

Note that if you change the project type on the app's Settings tab to a type that isn't compatible with your selected default stack, we'll automatically change the stack to a compatible one.

Log in to Bitrise and select Bitrise CI on the left, then select your project.
Click the Workflows button on the main page.
On the left, select Stacks & Machines.
In the Default Stack section, open the dropdown menu and select the stack you need.
Click Save changes in the top right corner.

Setting a Workflow-specific stack

When you set a stack for a Workflow, that Workflow will always run on that stack, regardless of the default stack.

Log in to Bitrise and select Bitrise CI on the left, then select your project.
Click the Workflows button on the main page.
On the left, select Stacks & Machines.
Scroll down to find the Workflow you need.
Select a stack.
Click Save changes in the top right corner.

Setting the machine type in the Workflow Editor

You can define the machine type you want to use for your build in the Workflow Editor. The available machine types depend on the type of stack you use: Table 1, “Bitrise build machine types”.

To set the machine type:

Log in to Bitrise and select Bitrise CI on the left, then select your project.
Click the Workflows button on the main page.
On the left, select Stacks & Machines.
In the Default Stack section, find the Machine type for the default stack section and choose a machine type.
Optionally, choose a Workflow-specific machine type for any Workflow that has a Workflow-specific stack set.

Setting the stack in the Configuration YAML

You can set both the default stack and Workflow-specific tasks in your project's Configuration YAML. Use the meta field with the appropriate stack ID:

meta:      
  bitrise.io:       
    stack: <stack-id>

This is particularly useful if you keep your bitrise.yml file stored in your app's repository.

Stack IDs

You can find the stack IDs on the top of each stack report: Bitrise stack reports. Alternatively, you can set a stack in the Workflow Editor and then check out the ID on the bitrise.yml tab, by finding the meta field.

The stack reports also show every pre-installed tool that is available on the stack.

Setting the default stack in the Configuration YAML

The default stack of your app is the stack that is used if you haven't set a specific stack for a Workflow.

Open your project's Configuration YAML.
Add a meta entry outside the workflows property or at the end of your Configuration YAML:
```
meta:      
  bitrise.io:       
    stack: 
```
Make sure you use double indentation.
Add the stack ID.

You can find the stack IDs on the stack reports page: the filenames without the .log extension are the stack IDs.
```
meta:      
  bitrise.io:       
    stack: <stack-id>
```

Setting Workflow-specific stacks in the Configuration YAML

When you set a stack for a Workflow, that Workflow will always run on that stack, regardless of the default stack.

Open your project's Configuration YAML.
Find the workflows property and find the name of the Workflow you need within.

Add a meta entry under the Workflow itself:

workflows:
  deploy:  
    meta:      
      bitrise.io:       
        stack:

Add the stack ID.

You can find the stack IDs on the top of each stack report page.

workflows:
  deploy:  
    meta:      
      bitrise.io:       
        stack: <stack-id>

Setting the machine type in the Configuration YAML

You can also define the machine type you want to use for your build in your project's Configuration YAML. Machine type refers to the hardware resources used in your build; for example, an Elite machine has more CPU cores and available RAM than a Standard machine.

To set the machine type in Configuration YAML file, you need to use the machine_type_id attribute in a meta entry:

Available machine IDs

You can find the available machine type IDs here: Build machine types.

Open your project's Configuration YAML file.
Find the workflows property and find the name of the Workflow you need within.

Add a meta entry:

# setting an 8-core Gen2 machine for an Xcode stack as the default machine type of the app:
meta:
  bitrise.io:
    machine_type_id: g2.8core
# setting a 12-core Gen2 machine as a Workflow-specific machine type
workflows:
  deploy:  
    meta:      
      bitrise.io:       
        machine_type_id: <machine-id>

Build machine types

Abstract

Bitrise offers multiple build machines with different specifications and credit costs. You can choose between them based on your needs.

You can track how much time you spent building your apps on each machine type with Insights: Bitrise CI metrics.

Machine availability by subscription plan

Not all machines are available on all subscription plans. Visit the pricing page to find out which machines are available on your plan!

Table 1. Bitrise build machine types

Operating system	Machine type name	CPU	RAM	Machine type ID for YAML configuration
macOS	M1 Medium	4 CPU @3.2GHz	6 GB	`g2-m1.4core`
	M1 Large	8 CPU @3.2 GHz	12 GB	`g2-m1.8core`
	M2 Pro Medium	4 CPU @3.49GHz	6 GB	`g2.mac.medium`
	M2 Pro Large	6 CPU @3.49GHz	14 GB	`g2.mac.large`
	M2 Pro X Large	12 CPU @3.49GHz	28 GB	`g2.mac.x-large`
	M4 Pro Large	7 CPU @4.52GHz	27GB	`g2.mac.4large`
	M4 Pro X Large	14 CPU @4.52 GHz	54 GB	`g2.mac.4x-large`
Linux	Medium	4 vCPU @3.1 GHz	16 GB	`standard`
	Large	8 vCPU @3.1 GHz	32 GB	`elite`
	X Large	16 vCPU @3.1 GHz	64 GB	`elite-xl`
	M	4 vCPU @3.7 GHz	16 GB	`g2.linux.medium`
	2M	6 vCPU @3.7 GHz	24 GB	`g2.linux.2medium`
	L	8 vCPU @3.7 GHz	32 GB	`g2.linux.large`
	4L	14 vCPU @3.7 GHz	56 GB	`g2.linux.4large`
	XL	16 vCPU @3.7 GHz	64 GB	`g2.linux.x-large`
	3XL	24 vCPU @3.7 GHz	96 GB	`g2.linux.3x-large`
	5XL	32 vCPU @3.7 GHz	128 GB	`g2.linux.5x-large`
	7XL	48 vCPU @3.7 GHz	192 GB	`g2.linux.7x-large`

In this section: