Knapsack Pro
Knapsack Pro
Bamboohttps://www.atlassian.com/software/bamboo |
Travis CIhttps://travis-ci.org |
|
|---|---|---|
| Unique feature |
Atlassian suite integration
|
Build Matrix, ease of use, GitHub integration
|
| Type of product |
On Premise
|
SaaS, Self-hosted / On Premise
|
| Offers a free plan |
Yes The full Atlassian suite is free for open source projects (https://www.atlassian.com/software/views/open-source-license-request). For all others, they offer a minimal free trial. |
Yes Free for open source projects |
| Predictable pricing |
Yes They price their product based on number of build agents (more concurrency, more expensive). Given the notoriety and depth of the Atlassian suite, the pricing can be steep for small companies. |
Yes Clearly defined monthly plans, depending on concurrent jobs needed. |
| Support / SLA |
Yes Dedicated tehnical support. |
Yes Available via email, or dedicated online interface for paid plans. |
|
Paralellism
Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro |
Yes Up to 100 parallel agents |
Yes TravisCI makes it very easy to split your build into different stages which are then run in parallel (ie: run integration tests separate from the unit tests). TravisCI calls this a build matrix: https://docs.travis-ci.com/user/build-matrix/. You can also very easily split tests accross several VMs using the knapsack_pro gem. |
|
Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines How to split tests in parallel in the optimal way with Knapsack Pro |
Yes Agents can run on multiple machines. |
N/A
|
| Containers support / Build environment |
Yes By default, they offer Docker support for the CI/CD job runners. |
Yes TravisCI runs each build in a isolated virtual machine. Pre-build packages include a few which support specific languages (Ruby and JavaScript included) or other software (Git, various databases), but vanilla packages such as Ubuntu Trusty are also available. |
|
Analytics / Status overview
Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project) |
Yes Excellent dashboards, even more so thanks to integrations with the other tools in the Atlassian arsenal |
Yes Available by default in Travis (this is what most of the web UI consists of) |
|
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes Great management support, built for large scale companies, even allows setting per-environment permissions (ie: QA team can only deploy to their own, isolated environment) |
N/A
|
| Self-hosted option |
Yes
|
Yes
|
| Hosted plans / SaaS |
No
|
Yes
|
|
Build pipelines
A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product. |
Yes Advanced pipeline support - with features built for feature branch support, various triggers, schedules, external notifications and more. |
No Specifically built around GitHub pull requests. Pipelines can be defined, but parts of the process need to be implemented separatelly in GitHub. |
|
Reports
Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard. |
Yes
|
Yes (partial) No persistent storage eliminates the possibility of code coverage reports on TravisCI alone. There is support for integrated 3rd parties such as Coveralls for reporting code coverage. |
|
Ecosystem
Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use? |
Yes Large selection (~200) of apps that integrate with Bamboo, available on the official marketplace for Bamboo: https://marketplace.atlassian.com/addons/app/bamboo |
No plugin support in TravisCI, plugins for other tools
|
|
Specific language support: Ruby
Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer. |
Yes (partial) It looks like the documentation and features for Ruby are lagging behind. All I could find is this repo: https://github.com/drscream/bamboozled-ruby-plugin, following this support ticket: https://jira.atlassian.com/browse/BAM-10948 from this documentation stub page: https://confluence.atlassian.com/bamboo0601/getting-started-with-ruby-and-bamboo-935580774.html |
Yes TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Ruby, starting from pre-built containers (with RVM already installed, for example) all the way to automatically running specific platform commands (such as detecting a Gemfile in the root of the project and automatically bundling dependencies). TravisCI also builds a Ruby SDK for easier use of the API. |
| Specific language support: JavaScript |
No No specific support, beyond some documentation on integrating Selenium (not marked as partial support since that documentation is only promoted in the Atlassian docs, but is hosted by BrowserStack) |
Yes TravisCI is designed to be a simple way to integrate CI/CD in your workflow so it has a couple of features aimed at specific languages, such as Javascript, starting from pre-built containers (with node already installed, for example) all the way to automatically running specific platform commands (such as detecting a package.json in the root of the project and running npm test) |
|
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Deep integration with the Atlassian product stack (Jira, etc.). |
Yes By default, TravisCI is built to work with GitHub. Additionally, there is strong support for 3rd party tools like Coveralls, BrowserStack, etc. |
|
API
Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options |
Yes
|
Yes Offers a feature-rich API that allows both reading data, as well as triggering or cancelling builds. |
| Auditing |
Yes
|
N/A
|
| Additional notes |
Not really something that should be purchased separatelly from the Atlassian stack. |
|