Rancher Pipelineshttps://rancher.com/docs/rancher/v2.x/en/project-admin/tools/pipelines/ |
AWS CodeBuildhttps://aws.amazon.com/codebuild/ |
|
---|---|---|
Unique feature |
DevOps tool for container orchestration
|
AWS integration
|
Type of product |
On Premise
|
SaaS
|
Offers a free plan |
Yes Free, open source project |
Yes The AWS free-tier includes 100 build-minutes per month, on their smallest machine. It's unclear, but it seems like this applies only to the first year of service. |
Predictable pricing |
Yes It's free! |
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. |
Support / SLA |
Yes Paid support available: https://rancher.com/pricing/ |
Yes
|
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 You can run multiple parallel steps within a build stage |
N/A
|
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 |
N/A Unclear from the documentation (probably not) |
N/A
|
Containers support / Build environment |
Yes
|
Yes Builds run in specific-to-the-project, isolated environments |
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 Not particularly clear, but it appears you can monitor stats in a Grafana dashboard: https://rancher.com/docs/rancher/v2.x/en/project-admin/tools/monitoring/ |
Yes Offers minimal information built in, but allows integrations with tools such as CloudWatch (another Amazon product), or streaming build information to your own API, for more in-depth analysis. |
Management support
How easy is it to manage users / projects / assign roles and permissions and so on |
Yes User management is available, with specific roles assigned, or permissions to certain resources and projects |
Yes Professional user management via AWS Identity and Access Management: https://aws.amazon.com/iam/ |
Self-hosted option |
Yes
|
No
|
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 Pipelines as code (YML files), but also manageable via the UI |
Yes As it's usually the case with Amazon, CodeBuild simply provides the 'build' part of a true CI/CD system, while pipelines are managed via CodePipeline, another Amazon product: https://aws.amazon.com/codepipeline/pricing/?nc=sn&loc=3 |
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 Offers minimal information built in, but allows integrations with tools such as CloudWatch (another Amazon product), or streaming build information to your own API, for more in-depth analysis. |
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? |
N/A
|
N/A
|
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. |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
No (partial) The environments available on CodeBuilt include Ruby pre-installed: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html, but that seems to be as far as specific support goes |
Specific language support: JavaScript |
N/A Pipelines / CI is just a small part of Rancher. No specific support mentioned. |
No (partial) The environments available on CodeBuilt include Node pre-installed: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html, but that seems to be as far as specific support goes |
Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc) |
Yes Integrations available for GitLab, GitHub and Bitbucket |
Yes CodeBuild builds can be connected to sources such as GitHub or BitBucket, but being an Amazon Service, the deepest integrations are with other Amazon Code services (CodePipeline, CodeDeploy, and others: https://aws.amazon.com/products/developer-tools/) |
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 REST API available. It provides introspection and documentation: https://github.com/rancher/api-spec/blob/master/specification.md#filtering. It should offer enough access to allow building whatever customizations or integrations with 3rd party tools deemed necessary. |
Yes Amazon SDKs can be used to interact with CodeBuild |
Auditing |
Yes Allows logging to various systems (Kafka, Elastic, etc) which should make audit possible |
Yes
|
Additional notes |
Rancher is a full software stack for container orchestration, going as far as building their own Linux distribution (RancherOS). Using Rancher seems more like a decision to be made considering all other features Rancher offers, not just the CI server. Also worth noting that Rancher uses Jenkins under the hood, but the engine is locked so projects can't just be migrated between the two. |
Like most things Amazon, it becomes more valuable as you acquire and integrate various Amazon solutions, not necesarily as a standalone tool. |