Central Services Portal is in Beta. We need your feedback to ensure the best possible user experience. Any feedback you provide will help us help you! Please use the feedback tool at the bottom of any page.

Search Icon

Central Services Portal is in Beta. We need your feedback to ensure the best possible user experience. Any feedback you provide will help us help you! Please use the feedback tool at the bottom of any page.

Mechanic

What is it?

Concourse Pipeline Mechanic is a CLI tool for creating new pipelines, updating existing ones, and tuning them for best practices and performance optimizations. Mechanic strives to provide sensible defaults so developers are never “starting from zero”. This enables devs to avoid wrestling with Concourse syntax and yaml formatting and instead focus on the custom parts of a pipeline, accomplishing in minutes or hours what previously might have taken days.

There is no onboarding needed to use Mechanic. It’s run on a developer machine in the root of a project and writes updates out to the local filesystem. Developers can use the changes provided by Mechanic as a starting point and modify the results as needed.

Who is it for?

Concourse Pipeline Mechanic is designed for developers who want to quickly and efficiently create and manage Concourse pipelines. It’s particularly useful for:

  • Concourse newcomers: Mechanic provides sensible defaults and simplifies the Concourse syntax, making it easier for developers to get started with pipeline creation.
  • Experienced Concourse users: Mechanic can help streamline the pipeline creation and update process, saving time and reducing the risk of errors.
  • Teams that want to standardize pipeline development: Mechanic can help establish best practices and ensure consistency across pipelines.

How to use it?

Updates created using Mechanic should go through a normal code commit and peer review cycle. Then developers can apply the changes to Concourse using the fly set-pipeline command.

wpChatIcon
wpChatIcon
Provide Feedback