Concourse Reviews

CodeClimate Reviews

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 / 9 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 / almost 1 year 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: about 1 year 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 / over 1 year ago

CodeClimate mentions (11)

• free-for.dev

  Codeclimate.com — Automated code review, free for Open Source and unlimited organisation-owned private repos (up to 4 collaborators). Also free for students and institutions. - Source: dev.to / over 1 year ago

• How To Use Code Climate To Improve Software Quality

  Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality. Source: almost 2 years ago

• RFC: A Full-stack Analytics Platform Architecture

  Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes... - Source: dev.to / about 2 years ago

• Adding coverage to CI pipeline?

  The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose. Source: over 2 years ago

• Node.js best practices list (July 2021)

  TL;DR: Using static analysis tools helps by giving objective ways to improve code quality and keeps your code maintainable. You can add static analysis tools to your CI build to fail when it finds code smells. Its main selling points over plain linting are the ability to inspect quality in the context of multiple files (e.g. Detect duplications), perform advanced analysis (e.g. Code complexity), and follow the... - Source: dev.to / almost 3 years ago