Knapsack Pro
Knapsack Pro
Bamboohttps://www.atlassian.com/software/bamboo |
Github Actionshttps://github.com/features/actions |
|
|---|---|---|
| Unique feature |
Atlassian suite integration
|
Best GitHub integration possible
|
| Type of product |
On Premise
|
SaaS / 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 The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan 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 (partial) While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows) |
| Support / SLA |
Yes Dedicated tehnical support. |
Yes Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support. |
|
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 Matrix builds allow concurrent jobs, even multi-platform. |
|
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 No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available. |
| Containers support / Build environment |
Yes By default, they offer Docker support for the CI/CD job runners. |
Yes Linux, macOS, Windows, and containers, or run directly in a VM. |
|
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 Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes. |
|
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 Unclear from the available documentation |
| Self-hosted option |
Yes
|
Yes Coming soon, not available yet. |
| 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. |
Yes Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that) |
|
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
|
N/A Unclear from the available documentation |
|
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 |
Yes Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions |
|
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 Unclear how, but they mention Ruby support specifically on the homepage |
| 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 Unclear how, but they mention Javascript (Node.js) support specifically on the homepage |
|
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 Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more) |
|
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
|
N/A Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available) |
| Auditing |
Yes
|
N/A
|
| Additional notes |
Not really something that should be purchased separatelly from the Atlassian stack. |
|