from Hacker News

Show HN: Pippy – Pipelines for GitHub Actions

by awenix on 7/17/24, 7:17 AM with 21 comments

I am excited to share pippy, which allows users to create configurable pipelines using Github Actions. If you have used Azure pipelines, in summary, this would be Azure Pipelines meets Github Actions.

Cloud version: https://app.pippy.dev/login (closed beta) I am also open sourcing command line version: https://github.com/nixmade/pippy.

Key features:

- Automatic Rollback

- Datadog Monitoring

- Pause/Resume

The product is built using open source orchestrator.

Orchestrator: https://github.com/nixmade/orchestrator

Orchestrator allows you to orchestrate rollout to specific set of targets and provide monitoring capabilities to optionally rollback. I hope to provide Cloud API so platforms can orchestrate updates using the framework.

Tech stack:

Database: Postgres

Backend: Golang

Frontend: React + Shadcn UI

Cloud: Azure container apps

Please leave your feedback in comments. Hope you can give the command line version a try, and sign up for beta of the cloud version.

  • by chuckadams on 7/17/24, 3:03 PM

    > Pipelines are sequence of GitHub Actions workflows, executed in order, waiting for successful execution of each workflow before processing to next workflow execution

    Isn't that exactly what an action already does? A lot of the features in the boxes below the fold also sound like things you get out of the box on GH. Triggering on push for example, that's probably how at least 90% of GH actions are run. I suggest you emphasize the parts that are actually novel, because the home page doesn't convey it at all.

    Also I know it's crazy nitpicky and certainly not unique to pippy.dev but I always want to click on those feature boxes for more info. They just look like interactive things, and it's unsatisfying when they're not.

  • by jitl on 7/17/24, 2:40 PM

    Your home page mostly focuses on stuff that I thought GitHub already provides. How do features like block for approval, locks, etc differ from the built in capabilities native to GitHub actions? We have a “service deploy” workflow that pauses for approval after preparing the deploy but before it’s installed on the cluster using stock actions. We also “lock” deploys without third party stuff. When it comes to “cloud api”, GitHub has an API for triggering action runs too.

    Here on HN you focus on monitor + rollback after deploy, which is more of a differentiator.

    (I didn’t watch the video)

  • by simonw on 7/17/24, 3:07 PM

    "If you have used Azure pipelines, in summary, this would be Azure Pipelines meets Github Actions."

    I haven't used Azure pipelines, could you explain for an audience that doesn't have that comparative knowledge?

    I know GitHub Actions pretty well but I'm having trouble understanding why I would want this extra layer on top of it.

  • by sleepybrett on 7/17/24, 7:02 PM

    After reading this site I can't tell what this actually does that github actions doesn't already do except the integration of a datadog exporter.. which we already did that in our shared workflows but w/ openmetrics/prometheus. Also what 'enterprise' only has 50 pipelines.

  • by stackskipton on 7/17/24, 2:55 PM

    Give me your Elevator Pitch for someone in Azure DevOps almost 100%. Even if some of teams moving to GitHub, we continue to leave their pipelines in Azure DevOps because it's so easy.

  • by orliesaurus on 7/17/24, 3:05 PM

    Would be cool if you can go deeper on the features on the homepage

  • by remolacha on 7/17/24, 8:11 PM

    Great concept. Needs a little refinement, but I really miss the ease-of-use of Azure DevOps now that I'm on GH. Excited to test it out

    Btw, is it open-source?

  • by mbladra on 7/17/24, 6:05 PM

    Seems interesting, but how is it different than what GitHub already does?