Go.CD vs Octopus Deploy

Overview

Octopus Deploy

Stacks407

Followers493

Votes118

GoCD

Stacks205

Followers325

Votes207

GitHub Stars7.3K

Forks980

Go.CD vs Octopus Deploy: What are the differences?

Introduction

Go.CD and Octopus Deploy are two popular continuous delivery tools used in software development. While both tools aim to simplify the process of deploying applications, there are key differences that set them apart. This article will highlight the main differences between Go.CD and Octopus Deploy in a concise manner.

Deployment Workflow: Go.CD follows a declarative approach to define deployment pipelines, where each stage describes the desired state. On the other hand, Octopus Deploy uses a more visual and flexible approach, allowing users to define their deployment process using a graphical interface. This provides more control and customization options in Octopus Deploy compared to Go.CD.
Integration Support: Octopus Deploy offers a wide range of integrations with popular development tools and platforms such as Jenkins, TeamCity, and Azure DevOps. It also provides built-in support for Docker, Kubernetes, and AWS. In contrast, Go.CD has fewer out-of-the-box integrations but compensates with a rich set of plugins for extensibility.
Environments and Configurations: Octopus Deploy allows for the creation of multiple environments, each representing a different state in the deployment lifecycle, such as development, staging, and production. This enables easy management of different configurations and promotes controlled deployments across environments. Go.CD offers a similar concept of environments but with a greater emphasis on enabling parallel deployment of applications, making it more suitable for complex setups.
Agent-Based Architecture: Go.CD follows an agent-based architecture, where agents are responsible for executing the tasks defined in the deployment pipeline. This architecture allows for distributed and scalable deployments across multiple machines. Octopus Deploy, on the other hand, uses a server-agent model, where the central server communicates with agents running on target machines. This architecture provides centralized control, but may be less scalable for large-scale deployments.
Security and Access Control: Octopus Deploy provides fine-grained access control, allowing users to define permissions at the team, project, and individual level. It also supports integration with external authentication providers such as Active Directory and Azure AD. Go.CD, while providing basic role-based access control, may require additional configuration or third-party tools for advanced security requirements.
Pricing and Licensing: Octopus Deploy follows a commercial model with different pricing plans based on the number of target deployment targets. Go.CD, on the other hand, is an open-source tool released under the Apache License. This makes Go.CD more cost-effective for organizations with larger deployment targets or those on a tight budget.

In summary, Go.CD and Octopus Deploy differ in their approach to defining deployment workflows, integration support, environment and configuration management, architecture, security and access control, as well as pricing and licensing models. The choice between the two tools depends on the specific requirements and preferences of the development team or organization.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Octopus Deploy, GoCD

Mohammad Hossein

Chief Technology Officer at Planally

Apr 17, 2020

Needs adviceon

Docker

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

545k views545k

Comments

Detailed Comparison

Octopus Deploy	GoCD
Octopus Deploy helps teams to manage releases, automate deployments, and operate applications with automated runbooks. It's free for small teams.	GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.
Deploy on-premises or to the cloud, securely;.NET, Java, PHP, Node, Ruby;Full API support;Approvals and manual intervention;Enable self-service deployments;Installs in minutes;Integrates with your build server;Free for small teams	Model complex workflows with dependency management and parallel execution; Easy to pass once-built binaries between stages; Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance; Manual triggers allow deployment any version at anytime. And it's securable and auditable; Run tests written in most languages or frameworks, provides informative testing report; Compare both files and commit messages across any two arbitrary builds; Eliminate Bottlenecks by providing trivial parallel execution across pipelines, platforms, versions, branches, etc.; Easily reuse pipeline configurations via template system.
Statistics
GitHub Stars -	GitHub Stars 7.3K
GitHub Forks -	GitHub Forks 980
Stacks 407	Stacks 205
Followers 493	Followers 325
Votes 118	Votes 207
Pros & Cons
Pros 30 Powerful 25 Simplicity 20 Easy to learn 17 .Net oriented 14 Easy to manage releases and rollback Cons 4 Poor UI 2 Management of Config 2 Config & variables not versioned (e.g. in git)	Pros 32 Open source 27 Pipeline dependencies 25 Pipeline structures 22 Can run jobs in parallel 20 Very flexible Cons 2 Horrible ui 2 Lack of plugins 1 No support
Integrations
Jenkins Azure DevOps TeamCity Jira Appveyor Bamboo	Docker Kubernetes Slack

What are some alternatives to Octopus Deploy, GoCD?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Related Comparisons

Go.CD vs Octopus Deploy: What are the differences?

Introduction

Deployment Workflow: Go.CD follows a declarative approach to define deployment pipelines, where each stage describes the desired state. On the other hand, Octopus Deploy uses a more visual and flexible approach, allowing users to define their deployment process using a graphical interface. This provides more control and customization options in Octopus Deploy compared to Go.CD.
Integration Support: Octopus Deploy offers a wide range of integrations with popular development tools and platforms such as Jenkins, TeamCity, and Azure DevOps. It also provides built-in support for Docker, Kubernetes, and AWS. In contrast, Go.CD has fewer out-of-the-box integrations but compensates with a rich set of plugins for extensibility.
Environments and Configurations: Octopus Deploy allows for the creation of multiple environments, each representing a different state in the deployment lifecycle, such as development, staging, and production. This enables easy management of different configurations and promotes controlled deployments across environments. Go.CD offers a similar concept of environments but with a greater emphasis on enabling parallel deployment of applications, making it more suitable for complex setups.
Agent-Based Architecture: Go.CD follows an agent-based architecture, where agents are responsible for executing the tasks defined in the deployment pipeline. This architecture allows for distributed and scalable deployments across multiple machines. Octopus Deploy, on the other hand, uses a server-agent model, where the central server communicates with agents running on target machines. This architecture provides centralized control, but may be less scalable for large-scale deployments.
Security and Access Control: Octopus Deploy provides fine-grained access control, allowing users to define permissions at the team, project, and individual level. It also supports integration with external authentication providers such as Active Directory and Azure AD. Go.CD, while providing basic role-based access control, may require additional configuration or third-party tools for advanced security requirements.
Pricing and Licensing: Octopus Deploy follows a commercial model with different pricing plans based on the number of target deployment targets. Go.CD, on the other hand, is an open-source tool released under the Apache License. This makes Go.CD more cost-effective for organizations with larger deployment targets or those on a tight budget.

Go.CD vs Octopus Deploy

Overview

Go.CD vs Octopus Deploy: What are the differences?