Hacker Release Management

Currently, when I want to update one of my hacker packages, I look through this process.

  • Click changes on github
  • Wait for travis-ci to start changing to make sure that I am not getting build errors.
  • Download to hackage
  • Mark the release in git.

Naturally, I want to take each of these steps only if the previous step is successful.

I guess other people have a similar workflow, is there something that takes all these steps? I could probably do (1), (3) and (4) in a script, although (2) I'm not so sure (that is, checking the results of travis-ci), but since this seems to be a common problem, I it was interesting if someone had already solved it, so I do not reinvent the wheel.

+5
source share

Source: https://habr.com/ru/post/1268498/


All Articles