Hacker News Reader

Comment by cjk | Hacker News Reader

Something I miss in particular about Heroku's git-push-to-deploy experience is that you'd know whether the build/deploy succeeded by the time the push finished.

Modern “GitOps”-based deployments that rely on webhooks or polling are fine, but it feels so disjointed to me to `git push` and then have to go watch some other system to see if the deploy succeeded.

View on HN

How do these modern gitops based deployments work?

I've got a bare repo to push into, with hooks to sync to the live repo and run the Makefile upon push. I just see the output of the make command upon running `git push`.

The most basic of workflows shows the deploy status. I think you'd have to specifically go out of your way to hide it?

The deploy happens asynchronously from the push. Instead of having a separate repo you push to in order to deploy, the main branch of the shared GitHub (or whatever) repo just gets automatically deployed whenever there's a push (or sometimes it's triggered by a tag). So there's no feedback at all on push.

Ah of course! In fact I even have one personal project with collaborators, and indeed I've set it to deploy on push using GitHub actions, and indeed there's no feedback.

Pushing straight to the prod server is nicer UX, but I guess that only works reasonably well with one person, or a very tiny team.

You could just stream the updates to the cli. You'd have to be okay with using a command that handles pushing for you.

It's not just about the updates. If the deploy fails, then your push should also fail. That way your deploy branch is always a reflection of what's actually deployed.

Reply on news.ycombinator.com