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

11–20 of 23 posts

Re: Show HN: Pippy – Pipelines for GitHub Actions

#11

Post by simonw »

awenix wrote: post #10
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.

It sounds like approvals might be the key feature that Pippy is adding on top of GitHub Actions.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#12

Post by awenix »

stackskipton wrote: post #3

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.

I have been made aware of deployments in Github https://docs.github.com/en/actions/deployment/targeting-diff... which offers similar functionality, without external monitoring or Rollback. The advantage of Azure devops is integration with Azure identity, making setup of approvals, reviewers easier.

pippy makes it easy to setup pipeline from simple workflows using UI (which Azure devops is good at), while in Github you may need to create a parent workflow which comprises of these individual simple workflows.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#14

Post by sleepybrett »

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.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#15

Post by sleepybrett »

simonw wrote: post #11
awenix wrote: post #10

Earlier quoted context omitted.

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.

It sounds like approvals might be the key feature that Pippy is adding on top of GitHub Actions.

GHA already has approvals.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#16

Post by awenix »

sleepybrett wrote: post #14

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.

Sorry about the site not being clear. Agree most of this is already offered by Github, I updated the site to have key differentiators

- Automatic rollback on monitoring failures

- Datadog monitoring, queries configured datadog monitors after the workflow execution upto 15mins (right now hard coded). Optionally rollback if monitors are in failed state. This is also achievable with having a Github Action workflow query datadog monitors and stop further stages.

Re: Show HN: Pippy – Pipelines for GitHub Actions

#19

Post by jaylane »

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…

came here to ask the same question

Re: Show HN: Pippy – Pipelines for GitHub Actions

#20

Post by awenix »

remolacha wrote: post #18

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?

Thanks for trying this out. The command line version is open source and completely free, its local only and interacts with Github only.

you can try it here https://github.com/nixmade/pippy

Post reply on HN