I've been working on a Concourse tutorial video series. One of the points I've made is that plugins are unsafe to compose. They need to know too much about each other to prevent interference.
Concourse instead composes on resources, which all have an identical interface (check, get, put). You can pretty much use any resource with any other resource if they achieve your purpose.
We're still calling Concourse "CI/CD", but folk are now jokingly referring to "Continuous Everything" at Pivotal. Because it really is becoming the first tool for everything. We're running large automatic tooling with small teams, because it's easy to extend and relatively easy to rearrange.
Disclosure: I work for Pivotal, which sponsors Concourse development.
You can watch and follow along on https://issues.jenkins-ci.org/browse/JENKINS-38805 and https://issues.jenkins-ci.org/browse/JENKINS-38494.
And the most annoying, when blue ocean is tailing a job thats running, it uses 100% cpu on safari.
Those are the biggest issues I find with it as of today, otherwise its great for a manager mode until then.
Also on Chrome and Firefox