You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/ci/compatibility.mdx
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,6 +113,7 @@ Depot CI executes GitHub Actions YAML workflows. The following tables list GitHu
113
113
|`success()`| Run if no failures | ✅ |
114
114
|`failure()`| Run if any failure | ✅ |
115
115
|`cancelled()`| Run if cancelled | ✅ |
116
+
|`case()`| Conditional value select | ✅ |
116
117
|`hashFiles()`| File hashing for caching | ✅ |
117
118
|`contains()`| String/array contains | ✅ |
118
119
|`startsWith()`| String prefix check | ✅ |
@@ -183,7 +184,7 @@ Custom runner images via the `snapshot` field aren't supported. You can still [b
183
184
184
185
### Runner labels
185
186
186
-
Only Depot `runs-on` labels are supported. Any label that Depot doesn't recognize is treated as`depot-ubuntu-latest`.
187
+
Only Depot `runs-on` labels are supported. Nonstandard labels become `depot-ubuntu-latest` and expressions are preserved as-is. For Depot CI sandbox sizes and labels, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
Copy file name to clipboardExpand all lines: content/ci/how-to-guides/custom-images.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,6 +89,8 @@ Available values for `size`:
89
89
| `32x128` | 32 | 128 GB |
90
90
| `64x256` | 64 | 256 GB |
91
91
92
+
For sandbox information and pricing, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
93
+
92
94
## Environment variable changes don't persist in custom images
93
95
94
96
For actions that set or change environment variables, you need to include the steps in both the image build workflow and the workflows that use the custom image.
Copy file name to clipboardExpand all lines: content/ci/overview.mdx
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ For the full compatibility matrix, see [Depot CI compatibility with GitHub Actio
135
135
136
136
## Pricing
137
137
138
-
Depot CI sandbox usage is tracked and billed by the second, with no one-minute minimum per run. The minutes included with each plan are based on the smallest sandbox size (2 CPUs/8 GB). See [Depot CI sandbox sizes](#depot-ci-sandbox-sizes).
138
+
Depot CI sandbox usage is tracked and billed by the second, with no one-minute minimum per run. The minutes included with each plan are based on the smallest sandbox size (2 CPUs/8 GB). The included plan minutes aren't a hard cap. Additional usage is billed automatically. For sandbox sizes and additional usage pricing, see [Depot CI sandboxes](#depot-ci-sandboxes).
139
139
140
140
|| Developer plan | Startup plan | Business plan |
@@ -151,13 +151,13 @@ Depot CI sandbox usage is tracked and billed by the second, with no one-minute m
151
151
152
152
Plans also include [container build](/docs/container-builds/overview) minutes and [GitHub Actions runner](/docs/github-actions/overview) minutes. See [Pricing](/pricing) for more about plan features and costs.
153
153
154
-
The Depot CI minutes included in your monthly plan are not a hard cap. Additional usage is billed automatically.
154
+
##Depot CI sandboxes
155
155
156
-
### Depot CI sandbox sizes
156
+
Depot CI runs your workflows in x86_64 sandboxes. Sandboxes can use from 2 CPUs/8 GB of memory up to 64 CPUs/256 GB of memory. The default sandbox image is based on Ubuntu 24.04.
157
157
158
-
Larger sandboxes consume your included Depot CI minutes faster and cost more per second for extra usage. For example, a 4-CPU sandbox uses 2 minutes for every 1 minute of running time.
158
+
Larger sandboxes consume the Depot CI minutes included in your plan faster and cost more per second for extra usage. For example, a 4-CPU sandbox uses 2 minutes for every 1 minute of running time.
159
159
160
-
Use the labels from the following table in the `runs-on` key of your workflow. Use the sandbox size when referencing a [custom image](/docs/ci/how-to-guides/custom-images).
160
+
Use a _Label_ from the following table in the `runs-on` key of your workflow. For [custom images](/docs/ci/how-to-guides/custom-images), use a _Sandbox size_ paired with a Depot Registry custom image URL in the `runs-on` key.
Depot CI doesn't provide sandboxes for Arm, macOS, or Windows. Labels for these runner types (as listed in [Depot GitHub Actions runner types](/docs/github-actions/runner-types)) aren't compatible with Depot CI.
Copy file name to clipboardExpand all lines: content/ci/quickstart.mdx
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,12 +57,16 @@ The command runs a preflight check, then copies and transforms your workflows:
57
57
1. Validates authentication and checks that the [Depot Code Access app](#connect-to-github) is installed with the correct permissions.
58
58
2. Discovers all workflow files in `.github/workflows/`.
59
59
3. Prompts you to select which workflows to migrate.
60
-
4. Copies selected workflows to `.depot/workflows/` and any local actions to `.depot/actions/`, applying compatibility fixes and adding inline comments for any changes.
60
+
4. Copies selected workflows to `.depot/workflows/` and any local actions to `.depot/actions/`, applies compatibility fixes, and adds inline comments for any changes.
61
61
62
62
After migration, the command reports any secrets and variables referenced by the migrated workflows. To import them, see [Import secrets and variables](#import-secrets-and-variables) below.
63
63
64
64
For a full description of flags and subcommands, see [`depot ci migrate`](/docs/cli/reference/depot-ci#depot-ci-migrate) in the Depot CLI reference.
65
65
66
+
### Sandbox sizes
67
+
68
+
The `depot ci migrate` command changes standard `ubuntu-24.x` or `ubuntu-latest` runner labels in your workflow to the equivalent Depot CI sandbox label and notes the change in the migrated file. Nonstandard labels become `depot-ubuntu-latest` and expressions are preserved as-is. For Depot CI sandbox sizes and labels, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
69
+
66
70
## Import secrets and variables
67
71
68
72
If your workflows reference GitHub secrets or variables, use `depot ci migrate secrets-and-vars` to import them into Depot CI:
@@ -71,7 +75,7 @@ If your workflows reference GitHub secrets or variables, use `depot ci migrate s
71
75
depot ci migrate secrets-and-vars
72
76
```
73
77
74
-
This creates a one-shot GitHub Actions workflow that reads your existing GitHub secrets and variables and imports them into Depot CI. The command prints a URL where you can monitor the import.
78
+
This command creates a one-shot GitHub Actions workflow that reads your existing GitHub secrets and variables and imports them into Depot CI. The command prints a URL where you can monitor the import.
75
79
76
80
You can also add secrets and variables manually with `depot ci secrets add` and `depot ci vars add`, or from the [Depot CI settings](https://depot.dev/orgs/_/workflows/settings) in the dashboard. See [Manage secrets and variables](/docs/ci/how-to-guides/manage-secrets-and-variables) for details.
Copy file name to clipboardExpand all lines: content/container-builds/build-parallelism.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ When the same instruction is being built multiple times on the same runner, you
121
121
122
122
When Build A starts building at 10:00 AM, it pulls the base image and runs `npm ci`, creating new layers. When Build B starts building just a minute later at 10:01 AM, BuildKit recognizes that it needs the same base image and has the same `npm ci` command. Instead of duplicating this work, Build B waits for Build A to complete those steps, then reuses the layers that Build A created.
123
123
124
-
The deduplication process generally improves overall efficiency, but can be confusing when monitoring individual build times. To avoid overwhelming a single build server, you can enable [build auto-scaling](./how-to-guides/autoscaling) to some particular maximum parallelism value.
124
+
The deduplication process generally improves overall efficiency, but can be confusing when monitoring individual build times. To avoid overwhelming a single build server, you can enable [build auto-scaling](/docs/container-builds/how-to-guides/autoscaling) to some particular maximum parallelism value.
125
125
126
126
#### Docker Bake for orchestrated builds
127
127
@@ -195,7 +195,7 @@ Trade-offs:
195
195
196
196
#### Configuration
197
197
198
-
For detailed instructions on enabling and configuring auto-scaling, see the [Auto-scaling documentation](./how-to-guides/autoscaling).
198
+
For detailed instructions on enabling and configuring auto-scaling, see the [Auto-scaling documentation](/docs/container-builds/how-to-guides/autoscaling).
Copy file name to clipboardExpand all lines: content/github-actions/runner-types.mdx
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,12 @@
1
1
---
2
-
title: GitHub Actions Runner types
2
+
title: Depot GitHub Actions runner types
3
3
ogTitle: Types of Depot-managed GitHub Action Runners
4
-
description: Depot offers several different types of GitHub Actions runners, depending on your CI job needs.
4
+
description: Depot offers several different types of GitHub Actions runners, depending on your needs.
5
5
---
6
6
7
-
Depot offers several different types of GitHub Actions runners, depending on your CI job needs. You can choose the type on a per-job basis by specifying the runner label in your `.github/workflows/*.yaml` file:
7
+
This page lists Depot GitHub Actions runner types and sizes. For Depot CI, see [Depot CI sandboxes](/docs/ci/overview#depot-ci-sandboxes).
8
+
9
+
Depot offers several different types of GitHub Actions runners. You can choose the type on a per-job basis by specifying the runner label in your `.github/workflows/*.yaml` file:
8
10
9
11
```yaml
10
12
jobs:
@@ -16,7 +18,7 @@ jobs:
16
18
17
19
**In-memory Disk Accelerator**:
18
20
19
-
Depot runners reserve a portion of the memory on the runner host for a disk accelerator, backed by a RAM disk. The accelerator acts as buffer between reading and writing to the root disk, which allows Actions runs to perform incredibly fast I/O operations, much quicker than the physical disk would allow.
21
+
Depot Linux and macOS runners reserve a portion of the memory on the runner host for a disk accelerator, backed by a RAM disk. The accelerator acts as buffer between reading and writing to the root disk, which allows Actions runs to perform incredibly fast I/O operations, much quicker than the physical disk would allow.
20
22
21
23
## Intel runners
22
24
@@ -71,7 +73,7 @@ The following labels are available:
71
73
72
74
## Windows runners
73
75
74
-
Windows runners use instances with Intel chips running Windows Server 2022 or Windows Server 2025. [Ultra Runners](/blog/introducing-github-actions-ultra-runners) aren't available for Windows runners.
76
+
Windows runners use instances with Intel chips running Windows Server 2022 or Windows Server 2025.
75
77
76
78
**Note**: We support the `depot-windows-latest` if you prefer to use an evergreen version. This label is currently an alias for Window Server 2025.
77
79
@@ -109,10 +111,10 @@ macOS runners use instances with M2 chips running macOS 14 or macOS 15. Their EB
**Note:** due to licensing constraints from Apple, our macOS runner capacity is not fully elastic like our other runner types. We periodically update capacity to match demand, but macOS jobs can experience longer queue times during times of high demand.
118
120
@@ -131,9 +133,9 @@ If you'd like to see what tools and software are installed in each runner image,
131
133
132
134
- [`depot-ubuntu-24.04`](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md) and `depot-ubuntu-latest`
_Note: We do our best to keep our images in sync with GitHub's, but there may be a slight delay between when GitHub updates their images and when we update ours. If you need a specific version of a tool or software, please check the links above to see if it's available in the image you're using._
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments