Skip to content
Permalink
Browse files

Fix documentation about USE_BAZELISK_MIGRATE (#865)

* Fix documentation about USE_BAZELISK_MIGRATE

Belongs to #859

* Update README.md
  • Loading branch information...
fweikert committed Oct 28, 2019
1 parent 8424931 commit 0112379e3737f771aa547f5d77168738200f461c
Showing with 10 additions and 1 deletion.
  1. +10 −1 buildkite/README.md
@@ -309,7 +309,7 @@ Similar to the aforementioned downstream pipeline you can configure individual p
runs your targets with all incompatible flags that will be flipped in the next major Bazel release and
prints detailed information about which flags need to be migrated.

You can enable this feature by adding the following code to the top of the pipeline configuration:
You can enable this feature by adding the following code to the top of the pipeline steps in Buildkite at https://buildkite.com/bazel/YOUR_PIPELINE_SLUG/settings, **not** in the pipeline configuration yaml file:

```yaml
---
@@ -325,6 +325,15 @@ env:
USE_BAZELISK_MIGRATE: FAIL
```

If you want to enable this feature for a single build, but not for the entire pipeline,
you can follow these steps instead:

1. Navigate to your pipeline in Buildkite.
1. Click on the "New Build" button in the top right corner.
1. Expand the pipeline options via a click on "Options".
1. Enter `USE_BAZELISK_MIGRATE=FAIL` into the "Environment Variables" text field.
1. Click on "Create Build".

### macOS: Using a specific version of Xcode

We upgrade the CI machines to the latest version of Xcode shortly after it is released and this

0 comments on commit 0112379

Please sign in to comment.
You can’t perform that action at this time.