From 65fb376e7e44da914aba35d98516914559b5be60 Mon Sep 17 00:00:00 2001 From: Daniel Jones Date: Tue, 18 Jan 2022 12:31:33 +0000 Subject: [PATCH] point out the Concourse is not great at PR workflows --- content/blog/ci-shootout-conclusion.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/blog/ci-shootout-conclusion.md b/content/blog/ci-shootout-conclusion.md index d567b1a0..ca8d96e1 100644 --- a/content/blog/ci-shootout-conclusion.md +++ b/content/blog/ci-shootout-conclusion.md @@ -304,6 +304,10 @@ The suite of Argo components combine to make provide a higher level of abstracti ## Concourse +### Pull request workflows + +Concourse has gotten better at visualising pull request-based workflows, but it's still not ideal. It was built with the opinions of its authors baked in, and they practised true continuous delivery (of which trunk-based development is a core tenet). [Instanced pipelines](https://concourse-ci.org/instanced-pipelines.html) make this sort of workflow easier to track, but we still haven't gotten to the [v10 vision](https://blog.concourse-ci.org/core-roadmap-towards-v10/). + ### Single pane of glass Concourse's user interface always shows you the latest version of a pipeline. It's perfectly suited to use as a build monitor, constantly displaying the current state of the world to a team.