Need advice about which tool to choose?Ask the StackShare community!

GoCD

208
326
+ 1
207
Snap CI

29
56
+ 1
100
Add tool

GoCD vs Snap CI: What are the differences?

Developers describe GoCD as "Open source continuous delivery tool allows for advanced workflow modeling and dependencies management". 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. On the other hand, Snap CI is detailed as "Build, test, and deploy software faster with Snap's continuous integration and deployment tool". 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.

GoCD and Snap CI can be primarily classified as "Continuous Integration" tools.

Some of the features offered by GoCD are:

  • 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

On the other hand, Snap CI provides the following key features:

  • Deployment Options - Heroku, AWS
  • System Libraries - Your build runs on a RedHat 6-compatible system with commonly required libraries
  • Customization Options - In addition to all that we support out of the box, we offer you the chance to customize your build extensively.

"Open source" is the top reason why over 29 developers like GoCD, while over 13 developers mention "Github integration" as the leading cause for choosing Snap CI.

GoCD is an open source tool with 5.07K GitHub stars and 796 GitHub forks. Here's a link to GoCD's open source repository on GitHub.

Auto Trader, Hazeorid, and OpenX are some of the popular companies that use GoCD, whereas Snap CI is used by Hazeorid, Firecracker, and Elerna. GoCD has a broader approval, being mentioned in 40 company stacks & 78 developers stacks; compared to Snap CI, which is listed in 8 company stacks and 21 developer stacks.

Advice on GoCD and Snap CI
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 520.5K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

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.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 503.3K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of GoCD
Pros of Snap CI
  • 32
    Open source
  • 27
    Pipeline dependencies
  • 25
    Pipeline structures
  • 22
    Can run jobs in parallel
  • 20
    Very flexible
  • 15
    Plugin architecture
  • 13
    Environments can keep config secure
  • 12
    Great UI
  • 10
    Good user roles and permissions
  • 9
    Supports many material dependencies
  • 7
    Fan-in, Fan-out
  • 6
    Designed for cd not just ci
  • 4
    Empowers product people to make delivery decisions
  • 2
    Flexible & easy deployment
  • 2
    Pass around artifacts
  • 1
    Build once
  • 14
    Github integration
  • 13
    Easy setup
  • 11
    Multi-stage pipelines
  • 10
    Continuous deployment
  • 9
    Easy ui
  • 9
    Great customer support
  • 8
    Automatic branch tracking
  • 7
    Automated and manual deploys
  • 5
    Console debugging
  • 5
    Pull request integration
  • 4
    Continuous delivery
  • 3
    Free for open-source
  • 2
    Better PR support

Sign up to add or upvote prosMake informed product decisions

Cons of GoCD
Cons of Snap CI
  • 2
    Lack of plugins
  • 2
    Horrible ui
  • 1
    No support
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is GoCD?

    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.

    What is 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.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention GoCD and Snap CI as a desired skillset
    What companies use GoCD?
    What companies use Snap CI?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with GoCD?
    What tools integrate with Snap CI?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to GoCD and Snap CI?
    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.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    Bamboo
    Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
    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.
    Concourse
    Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
    See all alternatives