4 ms·

I've seen something similar happen, switched to https://www.go.cd/ https://www.go.cd/

by Rafert 11y ago

jacques_chester 11y ago
GoCD is very difficult to version-control and the interface is, to put it politely, in need of some love. At Pivotal my colleagues working on Cloud Foundry poured a lot of engineering effort into making GoCD scale across multiple teams, repos, sites and so on, and it just never worked out. Alex Suraci wrote Concourse, dogfooded it on a project team, and now pretty much the whole of Cloud Foundry is being built with Concourse pipelines.
- dominotw 11y ago
  >now pretty much the whole of Cloud Foundry is being built with Concourse pipelines. What are some of your thoughts on, * How it compares to Jenkins pipeline plugin https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin * Could it have been written a jenkins plugin instead of a whole new CI software. I like some of the features of concourse pipeline but it doesn't have support for wide range of remoting/plugins that jenkins supports.
  - jacques_chester 11y ago
    I'll defer to the authors for their experiences with Jenkins: http://concourse.ci/concourse-vs.html http://concourse.ci/concourse-vs.html As for writing a plugin, no, it would not have been possible. Concourse has an entirely different model of operation and needs easy access to containerisation facilities to achieve it. Concourse doesn't really think in terms of "plugins". What you become accustomed to is wondering "is there a resource type for this?". Right now I work on a software repo with a moderately complex API for uploading final binaries and releasing them to clients to download. Instead of telling people to write scripts or install a plugin, I can point them to the resource that another team has written. "Just add the resource". Released software is now just a stream of events, no different from git commits, S3 files, points in time, Tracker stories etc etc. Every resource has the same interface so it makes it possible to click together stuff into clever combinations, rather than lashing together awkwardly and hoping it'll work.
- Rafert 11y ago
  Missed this reply - agree that the interface is confusing. Concourse looks promising!

I've seen something similar happen, switched to https://www.go.cd/ https://www.go.cd/

by Rafert 11y ago

I've seen something similar happen, switched to https://www.go.cd/ https://www.go.cd/

GoCD is very difficult to version-control and the interface is, to put it politely, in need of some love. At Pivotal my colleagues working on Cloud Foundry poured a lot of engineering effort into making GoCD scale across multiple teams, repos, sites and so on, and it just never worked out. Alex Suraci wrote Concourse, dogfooded it on a project team, and now pretty much the whole of Cloud Foundry is being built with Concourse pipelines.

dominotw 11y ago
>now pretty much the whole of Cloud Foundry is being built with Concourse pipelines. What are some of your thoughts on, * How it compares to Jenkins pipeline plugin https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin * Could it have been written a jenkins plugin instead of a whole new CI software. I like some of the features of concourse pipeline but it doesn't have support for wide range of remoting/plugins that jenkins supports.
- jacques_chester 11y ago
  I'll defer to the authors for their experiences with Jenkins: http://concourse.ci/concourse-vs.html http://concourse.ci/concourse-vs.html As for writing a plugin, no, it would not have been possible. Concourse has an entirely different model of operation and needs easy access to containerisation facilities to achieve it. Concourse doesn't really think in terms of "plugins". What you become accustomed to is wondering "is there a resource type for this?". Right now I work on a software repo with a moderately complex API for uploading final binaries and releasing them to clients to download. Instead of telling people to write scripts or install a plugin, I can point them to the resource that another team has written. "Just add the resource". Released software is now just a stream of events, no different from git commits, S3 files, points in time, Tracker stories etc etc. Every resource has the same interface so it makes it possible to click together stuff into clever combinations, rather than lashing together awkwardly and hoping it'll work.
Rafert 11y ago
Missed this reply - agree that the interface is confusing. Concourse looks promising!