@@ -10,7 +10,7 @@ The following pipeline will run `test.sh` inside a `app` service container using
10
10
steps :
11
11
- command : test.sh
12
12
plugins :
13
- - docker-compose#v5.4.1 :
13
+ - docker-compose#v5.5.0 :
14
14
run : app
15
15
` ` `
16
16
19
19
` ` ` yml
20
20
steps:
21
21
- plugins:
22
- - docker-compose#v5.4.1 :
22
+ - docker-compose#v5.5.0 :
23
23
run: app
24
24
command: ["custom", "command", "values"]
25
25
` ` `
@@ -30,7 +30,7 @@ The plugin will honor the value of the `COMPOSE_FILE` environment variable if on
30
30
steps:
31
31
- command: test.sh
32
32
plugins:
33
- - docker-compose#v5.4.1 :
33
+ - docker-compose#v5.5.0 :
34
34
run: app
35
35
config: docker-compose.tests.yml
36
36
env:
@@ -46,15 +46,15 @@ steps:
46
46
- plugins:
47
47
- docker-login#v2.0.1:
48
48
username: xyz
49
- - docker-compose#v5.4.1 :
49
+ - docker-compose#v5.5.0 :
50
50
build: app
51
51
push: app:index.docker.io/myorg/myrepo:tag
52
52
- wait
53
53
- command: test.sh
54
54
plugins:
55
55
- docker-login#v2.0.1:
56
56
username: xyz
57
- - docker-compose#v5.4.1 :
57
+ - docker-compose#v5.5.0 :
58
58
run: app
59
59
` ` `
60
60
71
71
- command: generate-dist.sh
72
72
artifact_paths: "dist/*"
73
73
plugins:
74
- - docker-compose#v5.4.1 :
74
+ - docker-compose#v5.5.0 :
75
75
run: app
76
76
volumes:
77
77
- "./dist:/folder/dist"
@@ -95,7 +95,7 @@ this plugin offers a `environment` block of its own:
95
95
steps:
96
96
- command: generate-dist.sh
97
97
plugins:
98
- - docker-compose#v5.4.1 :
98
+ - docker-compose#v5.5.0 :
99
99
run: app
100
100
env:
101
101
- BUILDKITE_BUILD_NUMBER
@@ -113,7 +113,7 @@ Alternatively, you can have the plugin add all environment variables defined for
113
113
steps:
114
114
- command: use-vars.sh
115
115
plugins:
116
- - docker-compose#v5.4.1 :
116
+ - docker-compose#v5.5.0 :
117
117
run: app
118
118
propagate-environment: true
119
119
` ` `
@@ -129,7 +129,7 @@ steps:
129
129
env:
130
130
COMPOSE_PROFILES: "frontend,debug"
131
131
plugins:
132
- - docker-compose#v5.4.1 :
132
+ - docker-compose#v5.5.0 :
133
133
run: app
134
134
` ` `
135
135
@@ -165,7 +165,7 @@ Alternatively, if you want to set build arguments when pre-building an image, th
165
165
steps:
166
166
- command: generate-dist.sh
167
167
plugins:
168
- - docker-compose#v5.4.1 :
168
+ - docker-compose#v5.5.0 :
169
169
build: app
170
170
args:
171
171
- MY_CUSTOM_ARG=panda
@@ -182,7 +182,7 @@ If you have multiple steps that use the same service/image (such as steps that r
182
182
steps:
183
183
- label: ":docker: Build"
184
184
plugins:
185
- - docker-compose#v5.4.1 :
185
+ - docker-compose#v5.5.0 :
186
186
build: app
187
187
push: app
188
188
@@ -192,7 +192,7 @@ steps:
192
192
command: test.sh
193
193
parallelism: 25
194
194
plugins:
195
- - docker-compose#v5.4.1 :
195
+ - docker-compose#v5.5.0 :
196
196
run: app
197
197
require-prebuild: true
198
198
` ` `
@@ -211,7 +211,7 @@ steps:
211
211
agents:
212
212
queue: docker-builder
213
213
plugins:
214
- - docker-compose#v5.4.1 :
214
+ - docker-compose#v5.5.0 :
215
215
build:
216
216
- app
217
217
- tests
@@ -225,7 +225,7 @@ steps:
225
225
command: test.sh
226
226
parallelism: 25
227
227
plugins:
228
- - docker-compose#v5.4.1 :
228
+ - docker-compose#v5.5.0 :
229
229
run: tests
230
230
` ` `
231
231
@@ -237,7 +237,7 @@ If you want to push your Docker images ready for deployment, you can use the `pu
237
237
steps:
238
238
- label: ":docker: Push"
239
239
plugins:
240
- - docker-compose#v5.4.1 :
240
+ - docker-compose#v5.5.0 :
241
241
push: app
242
242
` ` `
243
243
@@ -247,7 +247,7 @@ To push multiple images, you can use a list:
247
247
steps:
248
248
- label: ":docker: Push"
249
249
plugins:
250
- - docker-compose#v5.4.1 :
250
+ - docker-compose#v5.5.0 :
251
251
push:
252
252
- first-service
253
253
- second-service
@@ -259,7 +259,7 @@ If you want to push to a specific location (that's not defined as the `image` in
259
259
steps:
260
260
- label: ":docker: Push"
261
261
plugins:
262
- - docker-compose#v5.4.1 :
262
+ - docker-compose#v5.5.0 :
263
263
push:
264
264
- app:index.docker.io/myorg/myrepo/myapp
265
265
- app:index.docker.io/myorg/myrepo/myapp:latest
@@ -273,7 +273,7 @@ A newly spawned agent won't contain any of the docker caches for the first run w
273
273
steps:
274
274
- label: ":docker: Build an image"
275
275
plugins:
276
- - docker-compose#v5.4.1 :
276
+ - docker-compose#v5.5.0 :
277
277
build: app
278
278
push: app:index.docker.io/myorg/myrepo:my-branch
279
279
cache-from:
@@ -284,7 +284,7 @@ steps:
284
284
285
285
- label: ":docker: Push to final repository"
286
286
plugins:
287
- - docker-compose#v5.4.1 :
287
+ - docker-compose#v5.5.0 :
288
288
push:
289
289
- app:myregistry:port/myrepo/myapp:latest
290
290
` ` `
@@ -297,7 +297,7 @@ The values you add in the `cache-from` will be mapped to the corresponding servi
297
297
steps:
298
298
- label: ":docker: Build an image"
299
299
plugins:
300
- - docker-compose#v5.4.1 :
300
+ - docker-compose#v5.5.0 :
301
301
build: app
302
302
push: app:index.docker.io/myorg/myrepo:my-branch
303
303
cache-from:
@@ -308,7 +308,7 @@ steps:
308
308
309
309
- label: ":docker: Push to final repository"
310
310
plugins:
311
- - docker-compose#v5.4.1 :
311
+ - docker-compose#v5.5.0 :
312
312
push:
313
313
- app:myregistry:port/myrepo/myapp:latest
314
314
` ` `
@@ -325,7 +325,7 @@ The `docker` driver can handle most situations but for advance features with the
325
325
steps:
326
326
- label: ":docker: Build an image"
327
327
plugins:
328
- - docker-compose#v5.4.1 :
328
+ - docker-compose#v5.5.0 :
329
329
build: app
330
330
push: app:index.docker.io/myorg/myrepo:my-branch
331
331
cache-from:
@@ -347,7 +347,7 @@ By default, Builder Instances specified by `name` or that are created with `crea
347
347
steps:
348
348
- label: ":docker: Build an image"
349
349
plugins:
350
- - docker-compose#v5.4.1 :
350
+ - docker-compose#v5.5.0 :
351
351
build: app
352
352
push: app:index.docker.io/myorg/myrepo:my-branch
353
353
cache-from:
@@ -366,7 +366,7 @@ By default, Builder Instances specified by `name` or that are created with `crea
366
366
steps:
367
367
- label: ":docker: Build an image"
368
368
plugins:
369
- - docker-compose#v5.4.1 :
369
+ - docker-compose#v5.5.0 :
370
370
build: app
371
371
push: app:index.docker.io/myorg/myrepo:my-branch
372
372
cache-from:
@@ -392,7 +392,7 @@ A newly spawned agent won't contain any of the docker caches for the first run w
392
392
steps:
393
393
- label: ":docker: Build an image and push cache"
394
394
plugins:
395
- - docker-compose#v5.4.1 :
395
+ - docker-compose#v5.5.0 :
396
396
build: app
397
397
push: app:${DOCKER_REGISTRY}/${IMAGE_REPO}:cache
398
398
cache-from:
@@ -409,7 +409,7 @@ steps:
409
409
410
410
- label: ":docker: Build an image using remote cache"
411
411
plugins:
412
- - docker-compose#v5.4.1 :
412
+ - docker-compose#v5.5.0 :
413
413
build: app
414
414
cache-from:
415
415
- "app:type=registry,ref=${DOCKER_REGISTRY}/${IMAGE_REPO}:cache"
0 commit comments