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.
Support for e-mail, HipChat, Slack, Campfire, Flowdock, Grove, Webhook, and Github Status API. Support for Ruby, Python, Node, Dart, PHP, Java, Scala, Groovy, Clojure, and Go. Support for PostgreSQL, MySQL, MongoDB, Redis, Memcached, ElasticSearch, and SQLite. See More
CircleCI supports Heroku, AWS, Engine Yard, dotCloud, Fabric, Nodejitsu, AppFog, Capistrano, Rockspace, and Joynet. Integration with Heroku is solid with the ability to automatically deploy or merge branches. CircleCI is also very flexible with deployment arrangement allowing SSH key management, deployment freedom (including directly to a PaaS), using Capistrano, Fabric, arbitrary bash commands, auto-merging to another branch, or packaging code up to S3. See More
Circle CI's web UI is clean and easy to use. It gives all the information for a single build in a feed and gives the explanation for each step of the build, what it's doing and what the step is related to. On the top it displays author information and the time and date when the build was started and finished. This is all done by giving only the most essential information without clogging the screen. See More
CircleCI can be connected to any project that is hosted on GitHub by logging in using the GitHub OAuth and adding the desired repository. Whenever a new commit is pushed to GitHub, CircleCI runs the tests that have been already defined and if none of them fails, the build is deployed to the runtime environment. 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
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
This is called the Jenkins Long-Term Support (LTS) version and helps to provide the most stable and assuring version of the Jenkins CI possible. Every 3 months, a version (which has been deemed the most reliable by the community) is chosen. After this, its branched, well-tested features are added (if they are missing), it is tested with the new features, bug fixes are then carried out if necessary, and from there it is released as the official Jenkins LTS version. 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
AppVeyor's configuration (which is done from the .yaml file in the root of the project) is unfortunately very limited. The configuration is either tied to a branch or, in other cases, it's global. This limits the developer to a single build process. However, since you can use arbitrary scripts for building, all those limitations can be overcome. Configuration can also be done from the web UI without a .yaml file. See More
Well I suggest you check it out for yourself, but what I like most is that it's simple yet effective: no bells and whistles, simple black/grey/light-blue/white color scheme, it's immediately clear where you have to go for each specific task, and build settings pages are like that as well. Getting a 'standard' build running literally took me a minute the first time I used it. See More
The fact that it is based on Java does not hinder TeamCity's ability to support different build environments. TeamCity in fact supports a large number of languages and tools for each of those languages (build runners and test frameworks). Some of the languages/platforms that are supported include: Ruby, .NET, Java. See More
The user can easily compose dependencies between builds by adding snapshot and artifact dependencies, all on the one screen. All output of upstream builds is available to downstream builds. Triggering sets off the entire build chain and supports re-running of the portions of the chain that failed. 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. By using Docker agents, you can run multiple remote agents on the same host without conflicting requirements. This 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
The design is minimalistic and based on today's standarts on material design. It uses colors which are pleasing to the eye and displays the information in an ordered way. The main view shows the latest activity sorted in a chronological order, displaying commits and pushes. Every repo has it's own view, on the top there's the repo's name and a dropdown which displays the current branch with the ability to change to another branch or to create a new one. On the right there's a vertical menu with links to add a new file, show the history or to download the current repository. See More
There is no need to use coveralls or any other tool for code coverage visualization in Shippable: code coverage and test results are integrated into the product. JaCoCo is also supported as a first class citizen with rich reports and several levels of drill down. See More
Shippable natively supports Docker and integrates with all Docker registries like Docker Hub, Amazon ECR, GCR, Quay, etc. You can set up end to end DevOps automation and deploy to any Container Service like Amazon ECS, your Kubernetes clusters, Docker Cloud/Datacenter, GKE, etc. See More
You can add your credentials to your Shippable account to communicate with third party cloud providers, artifact repositories, notification providers etc. These are stored securely in an encrypted secrets store and your config only refers to them by name, No more exposing your credentials by accident. See More
Help millions of people make better decisions.
Each month, over 1.7 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.