Updated 20. Azure Devops pipelines (markdown)
parent
058b218e46
commit
7c9e8dbe07
@ -26,3 +26,12 @@ Each build generates the windows AND linux images (note that we could have two s
|
|||||||
|
|
||||||
We have **multiarch tags**, for the tags `dev`, `master` and `latest`, so you don't need to use `win-dev` or `linux-dev`, the tag `dev` will pick the right architecture automatically. Only this three tags have multiarch, **and they are the only tags intended to be used**. The tag `dev` is the most updated.
|
We have **multiarch tags**, for the tags `dev`, `master` and `latest`, so you don't need to use `win-dev` or `linux-dev`, the tag `dev` will pick the right architecture automatically. Only this three tags have multiarch, **and they are the only tags intended to be used**. The tag `dev` is the most updated.
|
||||||
|
|
||||||
|
## Release pipelines
|
||||||
|
|
||||||
|
We have an Azure Devops Release pipeline per microservice. Source artifact for the release is the build.
|
||||||
|
|
||||||
|
All releases pipelines are very similar, as we use Helm to deploy to Kubernetes:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user