Bruin CLI Step 2 of 4

End-to-End Pipeline: NYC Taxi

Guide overview
  1. Introduction to Bruin4 min
  2. 2Install Bruin & Create Your First Pipeline10 min
  3. 3Build the NYC Taxi Pipeline16 min
  4. 4AI-Assisted Development and Analysis12 min
PreviousIntroduction to BruinNextBuild the NYC Taxi Pipeline

Install and initialize Bruin

1) Install Bruin CLI

If you haven't already, install Bruin using the recommended curl command from the installation docs. Verify with:

bruin version

2) Install the VS Code / Cursor extension

Search for "Bruin" in the VS Code or Cursor extension marketplace and install it. This gives you the Bruin render panel, run controls, and lineage visualization.

3) Bruin MCP (recommended)

We'll set up the Bruin MCP in detail in Step 4: AI-Assisted Development, but we recommend installing it now so you can use AI assistance throughout the guide. See the Bruin MCP setup guide for instructions.

4) Initialize a project

Run bruin init and choose the default template. This creates a git-initialized project with:

  • .bruin.yml - with a DuckDB connection and a chess.com sample connection
  • .gitignore - with .bruin.yml listed
  • A sample pipeline with Python, YAML (ingestor), and SQL assets

5) Understand the .bruin.yml

The generated config defines your environments and connections. The DuckDB connection creates a local database file - no cloud setup needed.

6) Run the sample assets

Open each asset and click Run in the Bruin panel:

  1. Python asset - a simple "Hello World" script
  2. Ingestor asset - pulls data from chess.com using Bruin's built-in connector, with configurable start/end date intervals for incremental ingestion
  3. SQL asset - transforms the ingested data with a basic aggregation, depending on the ingestor asset

7) Observe dependencies

The SQL asset depends on the ingestor asset. When you run the full pipeline, Bruin runs them in the correct order based on the dependency graph.