Hacker News Reader

Comment by oneweekwonder | Hacker News Reader

> Need more? Pay for it!

or be willing to move vendor and re-implement the stuff.

For comparison my magic combination(and not all free or realistic for everyone):

  - gitlab
  - jenkins/looking into gl ci
  - linode/cloudafrica(ah-hah hosting is not free)
  - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution
  - irc(fine I will take your slack and use the irc-bridge pfftt)

View on HN

> - jenkins/looking into gl ci

Yup, definitely look into it. We just killed our last Jenkins instance last week after we found out that everyone eventually moved to the GitLab CI.

> - sentry is a tough one. We rolling a custom mqttwarn/zabbix solution

Why a tough one? I found Sentry easy to self-host. They have pretty good docs: https://docs.sentry.io/server/installation/

> - irc(fine I will take your slack and use the irc-bridge pfftt)

We ditched Slack for Mattermost. It's not entirely up to par (yet), but works for most use-cases. And there's an IRC bridge for it, too (https://github.com/42wim/matterbridge). Oh, and Mattermost comes bundled with GitLab in their omnibus.

> Why a tough one? I found Sentry pretty easy to self-host.

your right, sentry! It was tough thinking of alternatives.

- sentry is a tough one. We rolling a custom mqttwarn/zabbix solution

Sentry is open source, you can self-host it...

A tough one, in the sense of suggesting a better/other alternative. so sentry... gogogofireintehole

I really wanted to use Gitlab for my next side project, but Circle CI doesn't support them, and I really don't want to pay Travis for my shitty proj. Hopefully this changes some day soon.

Gitlab has great built in support for CI [0], and you can easily add and run your own CI runners [1].

[0]: https://docs.gitlab.com/ce/ci/README.html

[1]: https://docs.gitlab.com/ce/ci/runners/README.html

We use gitlab's built-in runners and pipelines for continuous deployment to kubernetes and it works very well. We self-host our repos but the same tools are available through the hosted version.

GitLab's built-in CI is very good, and simpler than Travis for some things.

You also have the option (unlike Travis) of registering your own runners in your project settings, and you can do this either on gitlab.com or another deployment, without needing to be an admin of the deployment - you can get a key for it in your own project's settings. I'm using this at work, where we have an internal GitLab that I'm not an admin of (and where the GitLab admins probably have no interest in running a CI system), to do a small bit of CI on some things using one of my team's servers as a runner.

irc is fine but if you want an alternative, you can look into riot/matrix (irc bridge), mattermost, rocket chat, etc.

For hosting, I am looking to host my own server for fun and learning.

Reply on news.ycombinator.com