Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
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. Although 400 plugins exist for Jenkins, that doesn't mean they are all well-maintained and up-to-date. See More
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. See More
There have been several complaints by users regarding the quality of the plug-ins found in Jenkins' official plugin repo. A lot of plugins found in the default plugin directory are no longer actively maintained and as a result, they may be incompatible with later versions of Jenkins or other plugins. See More
This is called the Jenkins Long-Term Support (LTS) version and helps to provide the most stable and the most assuring version of the Jenkins CI possible. About every three months a version which has been deemed the most reliable by the community is chosen. After this, it's branched, well-tested features are added if they are missing, it's then tested with the new features, bug fixes are done if necessary and then it's released as the official Jenkins LTS version. See More
Jenkins without plugins is almost useless. All plugins are treated equal and published almost right away. Because there is no process for testing Jenkins' integration, the overall Jenkins experience is not that great. Furthermore, Jenkins' core and plugins are released on a regular basis, all requiring instant restarts, meaning that updates appear more than once a day! See More
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 heavily relied upon, is almost non-existent. See More
Starting with Jenkins 2.0, the pipeline capability, which has been available as a plugin before this version, has been built 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. See More
Bamboo is made by Atlassian, the company that also made and maintains tools such as JIRA, Stash and BitBucket, so it's a given that they would integrate quite nicely. For example, when connecting Bamboo with Stash and JIRA, details like JIRA issues, commits, reviews and approvals follow each release from development to production. If HipCHat is part of the integration, team members get notified right away in addition to email notifications. See More
Bamboo is the only build server to offer first-class support for the "delivery" aspect of continuous delivery. Deployment projects automate the tedium right out of releasing into each environment, while letting you control the flow with per-environment permissions. See More
Bamboo allows using Docker containers to create build agents. Using Docker agents lets you run multiple remote agents on the same host without conflicting requirements. It makes it easier to duplicate and distribute changes to build agents, and to use scripts for creating and maintaining agents. How can you define and build your own image and push it to a registry to share?This is when Bamboo’s Docker tasks come into play. Docker tasks make it possible to build an image, run a container, and push a Docker image to a registry from within your build or deployment project. See More
Drone.io does not let developers configure two different projects against the same repository. Instead, one must fork that repository into a new one and use that to create a new Drone.io project. You could go around this with downstream deployments, it's a missing feature but it shouldn't hurt much. See More
Jenkins is a fork from Hudson and as such it inherits most of it's source code. But Jenkins has far more commits and is a lot more active on the development side than Hudson. A lot of plugin developers have also chosen to support Jenkins and develop their product for Jenkins only. See More
Since Jenkins and Hudson share much of the same code base, they also share many of the same features. Hudson is also very easy to install, just a single .war file which is run inside the root of the directory where Hudson will be installed. See More
Help millions of people make better decisions.
Each month, over 2.8 million people use Slant to find the best products and share their knowledge. Pick the tags you’re passionate about to get a personalized feed and begin contributing your knowledge.