3 ms·

We spent some time evaluating this on my team, and we're still experimenting with it. I like it a lot, but the project appears to be mostly unmaintained since

We spent some time evaluating this on my team, and we're still experimenting with it. I like it a lot, but the project appears to be mostly unmaintained since mid-2021, when the creator left it to work on a lispy CI/CD tool [0] that feels very complicated... not sure what's going on there. [0]: https://github.com/vito/bass https://github.com/vito/bass

gavmor 3y ago
I enjoyed working with concourse as the foundations of Pivotal's release engineering systems. We tried several other platforms, but ultimately concourse was tailor-made for Pivotal-style dev/ops ie highly technical, prioritizing version-control and CLIs over GUIs, with the wall-mounted "build monitor" as a first-class user. While Concourse wasn't explicitly a Pivotal product, shouldn't Conway's Law encourage us not to understate the influences of the Pivotal milieu? I don't doubt that VMware failed to nurture Concourse's maintenance post-acquisition. I hesitate to make sweeping statements about the legendary virtualization behemoth, but I personally doubt their commitment XP dev/ops culture. Edit: don't take my word for it, read someone more closely involved to this day, Nat Bennett https://www.simplermachines.com/some-facts-about-concourse/ https://www.simplermachines.com/some-facts-about-concourse/
natbennett 3y ago
There are folks still working on it but at this point it pretty much only gets updates that VMware needs to continue delivering Cloud Foundry. It looks dead-er than it is because the team hasn't explained this, so there's a giant list of work that won't ever get done just kinda... hanging out... on the README and in the issues list. I use it at work but it was already running when I got there. I also really like it but I'd be reluctant to stand it up somewhere new unless I was using it to run a Cloud Foundry. It has some operational issues and it is actually impossible to get an SLA if you're not also a VMware Cloud Foundry customer, and that costs a minimum of $50k per year.

gavmor 3y ago

I enjoyed working with concourse as the foundations of Pivotal's release engineering systems. We tried several other platforms, but ultimately concourse was tailor-made for Pivotal-style dev/ops ie highly technical, prioritizing version-control and CLIs over GUIs, with the wall-mounted "build monitor" as a first-class user. While Concourse wasn't explicitly a Pivotal product, shouldn't Conway's Law encourage us not to understate the influences of the Pivotal milieu? I don't doubt that VMware failed to nurture Concourse's maintenance post-acquisition. I hesitate to make sweeping statements about the legendary virtualization behemoth, but I personally doubt their commitment XP dev/ops culture. Edit: don't take my word for it, read someone more closely involved to this day, Nat Bennett https://www.simplermachines.com/some-facts-about-concourse/ https://www.simplermachines.com/some-facts-about-concourse/

natbennett 3y ago

There are folks still working on it but at this point it pretty much only gets updates that VMware needs to continue delivering Cloud Foundry. It looks dead-er than it is because the team hasn't explained this, so there's a giant list of work that won't ever get done just kinda... hanging out... on the README and in the issues list. I use it at work but it was already running when I got there. I also really like it but I'd be reluctant to stand it up somewhere new unless I was using it to run a Cloud Foundry. It has some operational issues and it is actually impossible to get an SLA if you're not also a VMware Cloud Foundry customer, and that costs a minimum of $50k per year.