From ad33fef0aefad985ddc251769ab3d16365315b3a Mon Sep 17 00:00:00 2001 From: eiximenis Date: Fri, 7 Jun 2019 14:18:09 +0200 Subject: [PATCH] added PR build section --- 20.-Azure-Devops-pipelines.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/20.-Azure-Devops-pipelines.md b/20.-Azure-Devops-pipelines.md index b833283..cecb866 100644 --- a/20.-Azure-Devops-pipelines.md +++ b/20.-Azure-Devops-pipelines.md @@ -37,6 +37,12 @@ Once the build pipeline is created in Azure Devops you can override some of its ![Editing the build pipeline](./img/azure-devops/edit-build.png) +## Pull Request Builds + +We have enabled the build pipelines for Pull Request. There are some differences between a normal build and the build triggered by a PR though: + +* The build triggered from a PR do not push the docker images to any docker registry. + ## Windows vs Linux images Each build generates the windows AND linux images (note that we could have two separated builds instead). Build pushes the images to [eshop Dockerhub](https://hub.docker.com/u/eshop/).