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: pages/pipelines/build_exports.md
+17-14Lines changed: 17 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,9 +86,20 @@ Your Buildkite Organization ID (UUID) can be found on the settings page describe
86
86
### Prepare your Google Cloud Storage bucket
87
87
88
88
* Read and understand [Google Cloud Storage security best practices](https://cloud.google.com/security/best-practices) and [Best practices for Cloud Storage](https://cloud.google.com/storage/docs/).
89
-
* Your bucket must have a policy allowing our Buildkite service-account access as described here and demonstrated in the example below¹.
89
+
* Your bucket must have a policy allowing our Buildkite service-account access as described here.
90
90
- Assign Buildkite's service-account `buildkite-production-aws@buildkite-pipelines.iam.gserviceaccount.com` the `"Storage Object Creator"`.
91
-
- Scope the `"Storage Object Creator"` role using IAM Conditions to limit access to objects matching the prefix `buildkite/build-exports/org=YOUR-BUILDKITE-ORGANIZATION-UUID/*`¹.
91
+
- Scope the `"Storage Object Creator"` role using IAM Conditions to limit access to objects matching the prefix `buildkite/build-exports/org=YOUR-BUILDKITE-ORGANIZATION-UUID/*`.
92
+
- Your IAM Conditions should look like this, with `YOUR-BUCKET-NAME-HERE` and `YOUR-BUILDKITE-ORGANIZATION-UUID` substituted with your details:
"description": "Allow Buildkite's service-account to create objects only within the build exports prefix",
99
+
}
100
+
```
101
+
102
+
Your Buildkite Organization ID (UUID) can be found on the [organization's pipeline settings](https://buildkite.com/organizations/~/pipeline-settings).
92
103
* Your bucket must grant our Buildkite service-account (`buildkite-production-aws@buildkite-pipelines.iam.gserviceaccount.com`) `storage.objects.create` permission.
93
104
* Your bucket should use modern Google Cloud Storage security features and configurations, for example (but not limited to):
94
105
- [Public access prevention](https://cloud.google.com/storage/docs/public-access-prevention) to prevent accidental misconfiguration leading to data exposure.
@@ -97,18 +108,6 @@ Your Buildkite Organization ID (UUID) can be found on the settings page describe
97
108
- [Object versioning](https://cloud.google.com/storage/docs/object-versioning) to help recover objects from accidental deletion or overwrite.
98
109
* You may want to use [GCS Object Lifecycle Management](https://cloud.google.com/storage/docs/lifecycle) to manage storage class and object expiry.
99
110
100
-
¹ Your IAM Conditions should look like this, with `YOUR-BUCKET-NAME-HERE` and `YOUR-BUILDKITE-ORGANIZATION-UUID` substituted with your details:
"description": "Allow Buildkite's service-account to create objects only within the build exports prefix",
107
-
}
108
-
```
109
-
110
-
Your Buildkite Organization ID (UUID) can be found on the settings page described in the next section.
111
-
112
111
### Enable build exports
113
112
114
113
To enable build exports:
@@ -117,3 +116,7 @@ To enable build exports:
117
116
1. In the _Exporting historical build data_ section, select your build export strategy (S3 or GCS).
118
117
1. Enter your bucket name.
119
118
1. Select _Enable Export_.
119
+
120
+
Once _Enable Export_ is selected, we perform validation to ensure we can connect to the bucket provided for export. If there are any issues with connectivity export will not get enabled and you will see an error in the UI.
121
+
122
+
Second part of validation is we upload a test file "deliverability-test.txt" to your build export bucket. Please note that this test file may not appear right away in your build export bucket as there is an internal process that needs to kick off for this to happen.
0 commit comments