Go Continuous Delivery is now open source (opens in new tab)

Both Go from TW and the other Go! Programming language[0] is older than the Go language from Google.

[0]http://en.wikipedia.org/wiki/Go!_(programming_language)

I'd used Go (continuous delivery) at University before I'd heard about Go(lang). Yes, whilst in the perfect world everything would be named a short, memorable, unqiue (,descriptive?) name - that's not the case. The two items in question are distinct enough that searching for golang vs go cd will produce relevant results.

How hilarious, considering Go-lang stole its name too.

Created an issue for that: https://github.com/gocd/gocd/issues/131

Let me throw my hat in the ring:

Title: Google Announces Go Programming Language

My snark: Poor choice for a name, it clashes with the board game Go.

ThoughtWorks first released the commercial product that would become Go in 2008. It was rebranded later, shortly after the public announcement of Golang. Yes, it was a confusing move, but at the time there was no reason to believe that a programming language might conflict with a continuous delivery tool. Golang has produced a large and robust community, so of course it's confusing now. But it didn't come out of nowhere.

Might be hard to do, since it has been around for a while, but here's the Github issue on the project about the name: https://github.com/gocd/gocd/issues/131

apparently Thoughtworks has been building the Go continuous delivery tool as a custom product from even before Google made Go! I think the word "GO" hasn't been trademarked yet.

It's definitely not Java only, but it's also not really a replacement for MSDeploy. Instead, Go would run MSDeploy as the last step in a deployment pipeline. Check out http://bit.ly/RSAz3U for an MS based pipeline (though sadly for your question not MSDeploy)

I hope this helps- but Go is not a build tool - but a deployment pipeline tool.

Go runs builds on your machines and can call out to various build tools- like Ant, Nant, rake - or if all else fails- the shell. So anything you can run on the command line of your machine (either windows or *nix) can be automated by Snap.

Have you looked at octopus deploy? (octopusdeploy.com/) We've switched over all of our server deployments to it and it's great.

The latest 14.1 release brings in ability to create task plugins. Exciting times ahead!

That's one of the big reasons for Going OSS.

Go was their (our) commercial product which initially started from CruiseControl as the base. Go is a whole different beast and has gained a lot of features over the years. Now, it has been open sourced as well.

The answer to this question probably deserves a blog post. But, as mentioned by @willejs here (https://news.ycombinator.com/item?id=7646496), Jenkins has a well established community of plugins and plugin writers and so, is quite extensible. Go has good visualisation and good modeling capability, allowing you to model complex build and deployment workflows using a combination of tasks running in parallel and serial.

Both have many more pros and cons. To do justice to it, it needs a blog post. Let's see. Maybe I'll write one soon.

EDIT: This mailing list post has some more information: https://groups.google.com/forum/#!searchin/go-cd/jenkins/go-...

Here's a google group topic talking about it. https://groups.google.com/forum/#!searchin/go-cd/jenkins/go-.... Hope it helps.

I replied to a similar question asked earlier on the current page. Here's the link: https://news.ycombinator.com/item?id=7647742

The name gocd has been getting quite a bit of traction on twitter and such, and that's the name of the GitHub repo. Searching for that might be more effective.

This should help: https://news.ycombinator.com/item?id=7647742. Plugins & API are not the strongest points of Go. But thats in our immediate roadmap: https://groups.google.com/forum/#!searchin/go-cd/roadmap/go-.... So it should improve soon!