ingestlayer/recipes

Monitor CI/CD build status in Postgres

Route the build results that matter — a failed pipeline on your main branch — to where the team will actually see it, without the green-build noise.

01source

sourcesdk.eventTypeScript SDK
matchci.build.finished

02pipeline · 1 steps

  • 01CTLfilter.matchstatus = failed on main only

03destinations · 1

  • towarehouse.pgPostgres
    tableevents.signups

the event

You emit ci.build.finished with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

  • repostring
  • branchstring
  • statusstringpassed | failed
  • commitstringsha
  • duration_msnumber

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit ci.build.finished
import { ingest } from "@ingestlayer/sdk";

await ingest("ci.build.finished", {
  repo:        process.env.GITHUB_REPOSITORY,
  branch:      process.env.GITHUB_REF_NAME,
  status:      job.status,
  commit:      process.env.GITHUB_SHA,
  duration_ms: job.duration,
});

route it to Postgres

Insert each event as a row into a table in your own Postgres.

  1. 01

    add the connection

    Paste a Postgres connection string. Connections originate from our EU region — allowlist those egress IPs on your database.

  2. 02

    point at a table

    Name the target table. Top-level event fields map to columns, and the full payload is also available as a jsonb column.

  3. 03

    map columns

    Match event fields to columns with $event.* references, or accept the default mapping into a typed events table.

in postgresdelivered
INSERT INTO events.signups
  (user_id, email, plan, source, payload)
VALUES
  ('u_018f', 'ada@acme.com', 'pro',
   'marketing-site', '{ … }'::jsonb);

notes

questions

Can I mute passing builds?
Filter to failures on protected branches, so a red main build pings the team and routine green runs don't.
Do I need a CI plugin?
No — emit the event from a final pipeline step with the SDK or a curl call. Any CI that can run a script can report.
Can I track build time over weeks?
Send every build to Postgres with duration_ms; the trend is then a query, independent of which builds alerted.
build this pipelineor read the quickstart →

CI/CD build status, routed elsewhere

more, into Postgres