Concourse VS Distiller

Concourse mentions (21)

• We built the fastest CI in the world. It failed

  > Imagine you live in a world where no part of the build has to repeat unless the changes actually impacted it. A world in which all builds happened with automatic parallelism. A world in which you could reproduce very reliably any part of the build on your laptop. That sounds similar to https://concourse-ci.org/ I quite like it, but it never seemed to gain traction outside of Cloud Foundry. - Source: Hacker News / 8 months ago

• Ask HN: What do you use to run background jobs?

  I used Concourse[0] for a while. No real complaints, the visibility is nice but the functionality isn't anything new. [0] https://concourse-ci.org/. - Source: Hacker News / 11 months ago

• How to host React/Next "Cheaply" with a global audience? (NGO needs help)

  We run https://concourse-ci.org/ on our own hardware at our office. (as a side note, running your own hardware, you realise just how abysmally slow most cloud servers are.). Source: 12 months ago

• Cicada - Build CI pipelines using TypeScript

  We use https://concourse-ci.org/ at the moment and have been reasonably happy with it, however it only has support for linux containers at the moment, no windows containers. (MacOS doesn't have a containers primitive yet unfortunately). Source: about 1 year ago

• Why I joined Dagger

  My first attempt was Concourse, a CI/CD system that scheduled pipelines written in declarative YAML. Choosing YAML for Concourse made it for all, but it was definitely not once; we had to constantly rework its declarative model to handle more use cases. As time went on I started to wonder if the final frontier was actually a “language for CI/CD.”. - Source: dev.to / about 1 year ago

Distiller mentions (0)