Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Pippy – Pipelines for GitHub Actions

pippy.dev

Post reply on HN
Print view View original

1–10 of 23 posts

Show HN: Pippy – Pipelines for GitHub Actions

#1

Post by awenix »

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.

Show HN: Pippy – Pipelines for GitHub Actions
pippy.dev

Re: Show HN: Pippy – Pipelines for GitHub Actions

#2

Post by jitl »

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)

Re: Show HN: Pippy – Pipelines for GitHub Actions

#4

Post by chuckadams »

> 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.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#6

Post by simonw »

"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.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#7

Post by 1oooqooq »

jitl wrote: post #2

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 a…

same. Read the features and assumed Github Actions were already Pipelines for GitHub Actions.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#8

Post by awenix »

jitl wrote: post #2

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 a…

If you are referring to https://docs.github.com/en/actions/deployment/targeting-diff..., unfortunately i haven't played with it, and agree that it does offer most of the features offered by the product. As you mentioned the differentiator is the automatic rollback and support for external monitoring (datadog as of now). Would love to learn more about how you are using Github actions so i can make the product better, if you can drop an email to hello @ nixmade.com

For Cloud API, my post have been a little confusing, was suggesting/hoping 3rd party services to integrate with open source orchestrator https://github.com/nixmade/orchestrator so they can have their own version of pippy (not Github Actions).

Re: Show HN: Pippy – Pipelines for GitHub Actions

#9

Post by awenix »

chuckadams wrote: post #4

> 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…

Thank you for the feedback. Agree that most of the features are offered as https://docs.github.com/en/actions/deployment/targeting-diff..., unfortunately i haven't played with it. Will improve the landing page to focus on the pieces different from what is offered by Github.

>but I always want to click on those feature boxes for more info

Sorry about that, will work on not using cards :( I do not have much design/UI experience, and the lack of it shows here.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#10

Post by awenix »

simonw wrote: post #6

"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.

Github does offer deployments https://docs.github.com/en/actions/deployment/targeting-diff... which is similar in comparison, but i feel there are lot of steps to go through to get this working and creating pipeline for simple workflows makes it hard.

Azure pipelines offered this by setting up reviewers, approvals, but reading more about Github deployments, they might be similar.

Post reply on HN