Help shape the future of Concourse Since Concourse CI was created, thousands of users worldwide have helped the project by opening issues, committing code, and providing feedback to the team that develops the product. This community involvement is priceless - thank you, Concourse community! đź‘Ź
One of the ways the Concourse team collects feedback is through our annual Community Survey. This lets us gather crucial information about how users deploy Concourse, how different use cases scale, and various configuration patterns.
Before the paint completely dries on the v10 roadmap, there is one last big unknown I want to explore in case it brings more clarity to our direction: generic tasks.
Resource types are a great way to share tools and integrations for others to use in their pipelines. Unfortunately, they’re basically the only way, and because resources are a very opinionated concept, the resource type interface is not always a good fit.
A long-term roadmap for the core design of Concourse, a general-purpose CI/CD tool.
Accompanying slides. Recommended viewing: episode 1 of Yu-Gi-Oh.
Concourse’s design philosophy is to be expressive, versatile, and safe while limited to a handful of simple, proven concepts. The design of these concepts should make good practices feel intuitive and bad practices feel uncomfortable.
Coming up with these designs can be very challenging. There are many different workflows and patterns across the software industry, and they each have to be deeply understood in order to know what the good and bad practices are.
As I mentioned last week, this was a short week for us in Canada due to the Civic Holiday. We did, however, manage to work on some pretty cool stuff!
With the release of 4.0.0, we’ve been shifting our new feature focus towards Operations and Runtime. We’re intentionally slowing down on UX to focus on regressions and UI polish for existing screens.
On to the update:
Core
Continued our work on “pinning” a version of a resource across the pipeline.