-
Notifications
You must be signed in to change notification settings - Fork 1
Azure devops
We are using Azure DevOps for build and release-management.
As noted in the Overview, we have one build pipeline for each service, and one for the Kubernetes provisioning configuration. There is also one for the CI-part, which runs on each commit to master and builds all the services and runs tests.
The Build configurations are specified in yml-format and checked into the repository. They are comprised of a series of pipelines, or build steps, which describes how an application should be built. In this repo the yml-files are in Infrastructure/pipelines.
There are numerous pipelines to choose from here, but we have mostly used the docker pipelines, as Docker itself is a build environment.
...
...
...
Note: It is also possible to create the Azure Container Registry connection as a Docker Hub-connection using the admin password (possible to enable in the Azure portal), but this will make the release pipeline unable to trigger builds automatically and impossible to get a list of image versions to deploy. Not recommended, but a possible gotcha when setting up.
...
...
...
...