MSmschrage·Apr 27, 2023Submission
Write CI/CD pipelines using TypeScript
1 points · Open discussioncicadahq
cicada
Rust2023–2023
cicadahq / cicada · Archived
cicada
Write CI/CD pipelines using TypeScript
3Distinct people
3Mentions
0Explicit recommenders
326GitHub stars
What to know before exploring
What it is
Write CI/CD pipelines using TypeScript
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 3-hour interval3 dated mentions
Observed mentions: 2023-04-25 17:10:56 UTC to 2023-04-27 18:10:07 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 25, 15:00 | 2023-04-25 15:00:00 UTC | 2023-04-25 18:00:00 UTC | 1 | 0 | 1 |
| Apr 25, 18:00 | 2023-04-25 18:00:00 UTC | 2023-04-25 21:00:00 UTC | 1 | 1 | 0 |
| Apr 25, 21:00 | 2023-04-25 21:00:00 UTC | 2023-04-26 00:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 00:00 | 2023-04-26 00:00:00 UTC | 2023-04-26 03:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 03:00 | 2023-04-26 03:00:00 UTC | 2023-04-26 06:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 06:00 | 2023-04-26 06:00:00 UTC | 2023-04-26 09:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 09:00 | 2023-04-26 09:00:00 UTC | 2023-04-26 12:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 12:00 | 2023-04-26 12:00:00 UTC | 2023-04-26 15:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 15:00 | 2023-04-26 15:00:00 UTC | 2023-04-26 18:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 18:00 | 2023-04-26 18:00:00 UTC | 2023-04-26 21:00:00 UTC | 0 | 0 | 0 |
| Apr 26, 21:00 | 2023-04-26 21:00:00 UTC | 2023-04-27 00:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 00:00 | 2023-04-27 00:00:00 UTC | 2023-04-27 03:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 03:00 | 2023-04-27 03:00:00 UTC | 2023-04-27 06:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 06:00 | 2023-04-27 06:00:00 UTC | 2023-04-27 09:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 09:00 | 2023-04-27 09:00:00 UTC | 2023-04-27 12:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 12:00 | 2023-04-27 12:00:00 UTC | 2023-04-27 15:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 15:00 | 2023-04-27 15:00:00 UTC | 2023-04-27 18:00:00 UTC | 0 | 0 | 0 |
| Apr 27, 18:00 | 2023-04-27 18:00:00 UTC | 2023-04-27 21:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesCicada: Write CI/CD Pipelines in TypeScript
3 points · Open discussionHi HN! I’m Grant, creator of (https://cicada.build). Cicada lets you write CI/CD pipelines in TypeScript and test them locally.
We built Cicada because of our own struggles building CI/CD pipelines. YAML is cumbersome, not type-safe, and does not scale well for large pipelines. Sharing logic across pipelines is hard and most providers don’t let you test your pipelines locally.
Cicada lets you
1. write your pipelines in a real programming language. Using TypeScript gives you type-checking, syntax highlighting, and in-line documentation out of the box. It also lets you extend your pipelines by hooking into the entire TypeScript ecosystem of packages and modules.
2. test your pipelines locally. All jobs are run in containers. This means you can test them with Docker/Podman. It also means you get great caching.
3. run your pipelines on our c
Read the rest
loud. Pipelines are checked into your repository and run when triggered by an event in your repository (like a commit/PR), when triggered manually, or at a defined schedule.
We use Deno [0] to create pipeline definitions, Docker Buildkit [1] as our build engine, and Fly [2] for our cloud hosting. Our CLI is written in Rust for speed and stability. The hardest technical challenge we faced was writing BuildKit bindings for Rust [3].
Cicada’s client is fully MIT OSS (the CLI, BuildKit integration, and SDK) [4]. Our dashboard and cloud runners are closed source. The cloud runners have a generous free tier for individuals and are cheap and easy for teams.
You can create and run your first pipeline on your local device by running `npm install -g @cicadahq/cicada`. You can also learn more in our docs (https://cicada.build/docs) or by joining our Discord (https://cicada.build/discord).
In the meantime, I’d love to hear your feedback on what we’ve built!
[0] https://deno.land/
[1] https://docs.docker.com/build/buildkit/
[2] https://fly.io/
[3] https://github.com/cicadahq/buildkit-rs
[4] https://github.com/cicadahq/cicada