Starting with Jenkins 2.0, the pipeline capability which has been available as a plugin before this version, has been built-in into Jenkins itself. This allows developers to describe their chain of automation in text form, which can be version controlled and put alongside the source tree.
Jenkins has been in development since 2004 and is one of the most popular tools of it's kind. This means the technology is very mature and there are a lot of documentation and resources available for it.
The most useful information found about Jenkins is on StackOverflow and various strange corners of the internet that careful Googling may sometimes find. The actual documentation for Jenkins is poorly organized and extremely vague and outdated. Documentation for plugins, even the plugins most heav...
Unlike some of the simple and hosted alternatives, users need to host and setup Jenkins by themselves. This results in both a high initial setup time as well as time sunk into maintenance over a projects duration.
The flip side of "highly customizable" is that things most people want to do still require plugins not installed out-of-the-box. Worse, some common capabilities will require multiple plugins to get working right. The overhead of adding so many plugins amplifies many of the other cons.
Resources are to Concourse as plugins are to Jenkins. In other words, resources allow Concourse CI to do just about any work necessary in a build. But resources follow a "service provider interface" that makes them easy to build in any language (not just JVM languages) and have a clearly...
The downside of building on BOSH is that a full, scalable deployment of Concourse CI requires AWS, vSphere, or OpenStack. If you don't already have these, any one of them can be a big effort to set up, just to get a build server running. Might not be a good fit for smaller teams.