July 17th, 2024

Show HN: Pippy – Pipelines for GitHub Actions

Pippy enhances GitHub Actions with configurable pipelines, offering features like automatic rollback, monitoring, approvals, and more. Pricing ranges from free to paid plans, including add-ons for enhanced functionality. Users can sign up to optimize workflow control.

Read original articleLink Icon
Show HN: Pippy – Pipelines for GitHub Actions

Pippy is a tool that enhances GitHub Actions by allowing users to create configurable pipelines using workflows. These pipelines are sequences of GitHub Actions workflows that are executed in order, with each workflow waiting for successful completion before moving on to the next one. Pippy offers features like automatic rollback, Datadog monitoring, approvals, locks, pause/resume capabilities, automatic triggers, unlimited pipelines with unlimited stages, history of pipeline runs, audits, and more. The pricing for Pippy ranges from a free personal account with limitations to a paid Teams plan for $99/month and an Enterprise plan with custom pricing. Additionally, Pippy provides add-ons like a 100 pipeline runs pack and user-based pricing. Users can sign up for Pippy to supercharge their GitHub Actions and gain better control over their workflow executions.

Link Icon 9 comments
By @chuckadams - 3 months
> 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 - 3 months
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 - 3 months
"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 - 3 months
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 - 3 months
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 - 3 months
Would be cool if you can go deeper on the features on the homepage
By @remolacha - 3 months
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 - 3 months
Seems interesting, but how is it different than what GitHub already does?