Hacker News Reader

Comment by karterk | Hacker News Reader

I have worked with many open and proprietary CI tools, and find GoCD to be the best in this space right now. It supports both Continuous Integration and Continuous Delivery. They also made it open source last year:

https://www.go.cd/

View on HN

do you work for thoughtworks?. Every single post about Jenkins ends up with bunch of people from thoughtworks blindly shilling for their ci software.

Do you guys mind not doing that please?

Those of us at Pivotal come and rave about Concourse. So I guess it evens out.

GoCD was an important step forward conceptually. It's just an actually awful piece of software to try and use.

This seemed like quite the assumption, so I did some light digging. This person definitely does not work for ThoughtWorks.

I observed this pattern from previous jenkins posts.

But I did some digging after your comment and there it is

http://www.indix.com/blog/life-at-indix/employee-spotlight-k...

  What did you do before Indix?
  I was working at ThoughtWorks as a software engineer.

Well done I guess :) I worked briefly at ThoughtWorks, but definitely don't have any vested interests. ThoughtWorks produces not-so-great products too (like Mingle), but Go CI is definitely a great piece of software. And, I say that as someone who also has used Jenkins a lot.

Also, it's now completely open source. I'm not even trying to advocate an enterprise product.

What's the difference between Continuous Integration and Continuous Delivery?

CI is about the automation of testing code changes before they are merged into the main branch of development. CD is about deploying changes automatically in a live environment.

There are two CDs: - Continuous Delivery - Continuous Deployment

The first one just delivers the packages, but the deployment is triggered by human.

Reply on news.ycombinator.com