refined-ghost-4478
09/20/2024, 12:17 AMkapa
, but its even more confusing now: https://discord.com/channels/817392104711651328/1286475762114887680refined-ghost-4478
09/20/2024, 1:36 AMscratch
image, while for testing regular. In some cases we do not want to have whole toolchain in containerrefined-ghost-4478
09/20/2024, 1:40 AMscratch
image is way to go without any building testing/toolchainchilly-gigabyte-83853
09/24/2024, 12:12 PMdev
) and one for the production deploy (prod
).
In here I use a service called frontend
as an example but it should be easy to port to your case.
We then describe a Test action that uses the dev
image, specified as output of the dev
build action.
kind: Build
name: frontend
type: container
description: Build the frontend image.
[...]
spec:
dockerfile: frontend.dockerfile
targetStage: prod
---
kind: Build
name: frontend-dev
type: container
description: Build the frontend image using the dev stage.
[...]
spec:
dockerfile: frontend.dockerfile
targetStage: dev
---
kind: Test
type: container
name: frontend-test
dependencies:
- build.frontend-dev
spec:
image: ${actions.build.frontend-dev.outputs.deploymentImageId}
args: [npm, run, test]
chilly-gigabyte-83853
09/24/2024, 12:15 PMchilly-gigabyte-83853
09/24/2024, 12:16 PMrefined-ghost-4478
09/24/2024, 5:06 PMchilly-gigabyte-83853
09/25/2024, 9:46 AM