A visual CI/CD system

Name: A visual CI/CD system
Availability: InStock
Author: sebastian_io

by sebastian_io·Apr 22, 2026·7 points·2 comments

Visit Project View on HN

AI Analysis

●●SolidEye CandyBold Bet

Visual graph editor replaces YAML spaghetti; Perforce support matters for game studios.

Strengths

•Graph file format lets AI agents generate pipelines without hallucinating CLI flags.
•Perforce P4 support alongside Git/GitLab serves game dev teams most CI tools ignore.
•Group nodes collapse entire workflows into reusable blocks with defined inputs and outputs.

Weaknesses

•Visual CI/CD has been attempted many times; GitHub Actions UI already exists.
•Migration friction from existing YAML pipelines is high; no import tool mentioned.

Post Description

Over a year ago I started Actionforge, a managed/self-managed visual CI/CD platform. Just for fun, because I like building and experimenting with dev tools. Back then I thought the user would be a human with a keyboard and a mouse.

These days I rarely write pipelines. I mostly write specs, an agent dumps 500 lines of YAML, Python and a Makefile then I get my artifacts. The amount is overwhelming and a liability, and I stop trusting what I just merged. So I pivoted my CI/CD project toward more visualization, analytics and data aggregation, so engineers can see what agents and the pipeline produced, the flow, steps, data. Where it fails. With that I have a better mental model instead of a blob of code.

The goal is better observability, and pipelines that explain their own failures back to the next agent. And also with a personal focus on UX and design. My project supports Perforce P4, Git/GitHub and GitLab, so quite flexible.

Would love to hear your impression.

I'm also very interested in your CI/CD horror stories, and how you use them these days. Any input is much appreciated!

P.S. Code is public and provides GitHub Attestations.