forked from elastic/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
catalog-info.yaml
208 lines (199 loc) · 6.06 KB
/
catalog-info.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
---
# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/rre.schema.json
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-docs
description: Build and Publish the docs
links:
- title: Pipeline
url: https://buildkite.com/elastic/docs-build
spec:
type: buildkite-pipeline
owner: group:docs
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: docs / build
spec:
repository: elastic/docs
pipeline_file: ".buildkite/build_pipeline.yml"
branch_configuration: master
provider_settings:
build_pull_requests: false
schedules:
periodic_docs_build:
branch: "master"
message: "Build the docs every 30 minutes"
cronline: "*/30 * * * *"
teams:
docs-build-guild:
access_level: MANAGE_BUILD_AND_READ
ci-docs-migration-taskforce:
access_level: MANAGE_BUILD_AND_READ
docs:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
env:
ELASTIC_SLACK_NOTIFICATIONS_ENABLED: "true"
SLACK_NOTIFICATIONS_CHANNEL: "#docs-builds"
SLACK_NOTIFICATIONS_ALL_BRANCHES: "false"
SLACK_NOTIFICATIONS_ON_SUCCESS: "false"
---
# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/rre.schema.json
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-docs-pr
description: Build the docs on pull requests to the `elastic/docs` and products docs repositories.
links:
- title: Pipeline
url: https://buildkite.com/elastic/docs-build-pr
spec:
type: buildkite-pipeline
owner: group:docs
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: docs / build-pr
spec:
repository: elastic/docs
pipeline_file: ".buildkite/build_pr_pipeline.yml"
skip_intermediate_builds: false
provider_settings:
# Trigger mode should be set to `none` since this job should only be triggered by API from the buildkite-pr-bot
# But doing so, we hit this bug: https://forum.buildkite.community/t/request-build-error-branches-have-been-disabled-for-this-pipeline/1463
# So we set the `deployment` trigger which we never use and seem to allow API triggers
trigger_mode: "deployment"
teams:
docs-build-guild:
access_level: MANAGE_BUILD_AND_READ
ci-docs-migration-taskforce:
access_level: MANAGE_BUILD_AND_READ
docs:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
# Declare daily preview cleaner
---
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-docs-preview-cleaner
description: Daily Preview Cleaner
links:
- title: Pipeline
url: https://buildkite.com/elastic/docs-preview-cleaner
spec:
type: buildkite-pipeline
owner: group:docs
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: docs / preview-cleaner
spec:
repository: elastic/docs
pipeline_file: ".buildkite/preview_cleaner_pipeline.yml"
env:
ELASTIC_SLACK_NOTIFICATIONS_ENABLED: "true"
SLACK_NOTIFICATIONS_CHANNEL: "#docs-builds"
SLACK_NOTIFICATIONS_ALL_BRANCHES: "false"
SLACK_NOTIFICATIONS_ON_SUCCESS: "false"
provider_settings:
trigger_mode: none
schedules:
Daily Run:
branch: "master"
cronline: "0 6 * * *"
message: "Runs daily preview cleaning."
teams:
docs-build-guild:
access_level: MANAGE_BUILD_AND_READ
ci-docs-migration-taskforce:
access_level: MANAGE_BUILD_AND_READ
docs:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
# Declare test execution on PR and merge to master
---
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-docs-test
description: Run tests on PR and merges
links:
- title: Pipeline
url: https://buildkite.com/elastic/docs-test
spec:
type: buildkite-pipeline
owner: group:docs
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: docs / test
spec:
branch_configuration: master
repository: elastic/docs
pipeline_file: ".buildkite/test_pipeline.yml"
teams:
docs-build-guild:
access_level: MANAGE_BUILD_AND_READ
ci-docs-migration-taskforce:
access_level: MANAGE_BUILD_AND_READ
docs:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
env:
ELASTIC_SLACK_NOTIFICATIONS_ENABLED: "true"
SLACK_NOTIFICATIONS_CHANNEL: "#docs-builds"
SLACK_NOTIFICATIONS_ALL_BRANCHES: "false"
SLACK_NOTIFICATIONS_ON_SUCCESS: "false"
# Declare build air-gapped
---
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-docs-build-air-gapped
description: Build air-gapped
links:
- title: Pipeline
url: https://buildkite.com/elastic/docs-build-air-gapped
spec:
type: buildkite-pipeline
owner: group:docs
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: docs / build air-gapped
spec:
repository: elastic/docs
pipeline_file: ".buildkite/air_gapped_pipeline.yml"
provider_settings:
trigger_mode: none
schedules:
Daily Run:
branch: "master"
cronline: "0 5 * * *"
message: "Daily push image to registry."
teams:
docs-build-guild:
access_level: MANAGE_BUILD_AND_READ
ci-docs-migration-taskforce:
access_level: MANAGE_BUILD_AND_READ
docs:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY