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

Releases – a workflow for shipping software to end users

github.com

Post reply on HN
Print view View original

11–20 of 82 posts

Re: Releases – a workflow for shipping software to end users

#12

Post by JangoSteve »

secure wrote: post #8

While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…

That's actually what I set out to solve with jspkg.com, at least for JavaScript and CSS based projects. I'd say I've gotten to about 20% done toward that goal. Currently the site allows you to select a git tag from your repo and it will automatically package it up for you and keep track of downloads, archive old releases, etc.

Re: Releases – a workflow for shipping software to end users

#14

Post by DanielRibeiro »

xpaulbettsx wrote: post #11

Here's a few examples of Releases: https://github.com/reactiveui/reactiveui/releases https://github.com/github/akavache/releases https://github.com/xpaulbettsx/splat/releases

Link form:

https://github.com/reactiveui/reactiveui/releases

https://github.com/github/akavache/releases

https://github.com/xpaulbettsx/splat/releases

Re: Releases – a workflow for shipping software to end users

#17

Post by mrud »

secure wrote: post #8

While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…

jenkins or any other of the continuous integration solutions

Re: Releases – a workflow for shipping software to end users

#18

Post by ejdyksen »

jeremymcanally wrote: post #13
ejdyksen wrote: post #3

Cool! We finally have downloads back! It looks like this fails on tag names that have a slash in them.

Whoops. File a support ticket (e-mail support@github.com), please! That'd be uber helpful.

Done and done. Thanks!

Re: Releases – a workflow for shipping software to end users

#19

Post by mskierkowski »

secure wrote: post #8

While on the subject: does anyone know a software/service for automating software releases? I usually perform these steps manually: create a new tag, merge the “next” branch into the “master” branch, run “make dist” from a clean checkout, do a handful of sanity checks on the result, gpg-sign it, push it into a separate git repository for the website, archive the current docs in the website, update the website’s docs…

Factor.io might be a good fit for you. I am the co-founder/CEO and I hate self promoting, but in this case I think that we can help. We provide a way for you to create workflows like the one you described. It's kind of like IFTTT/Zapier for Dev/DevOps. But we support running numerous actions, custom code for new extensions, and more complex operations. Still in private beta, but would love to help out and get you to test it out. Shoot me an email maciej@factor.io.

Re: Releases – a workflow for shipping software to end users

#20

Post by philipn »

Is there any way to add the release notes via a git commit? This is very nice, but it introduces further dependence on GitHub if something like that isn't possible. I suppose as long as there's API access someone could / will write an exporter, though. Anyway, great stuff either way!
Post reply on HN