Skip to content

Comment on Setting Up a Jenkins Home Labparent

Comments

Second this... As someone who's a very small start-up the GitLab CI/CD pipelines are SO much more simple/manageable vs. anything I've ever done with Jenkins.

I self-host GitLab on Linode with a single runner in the cloud (and sometimes use runners on my local machines to speed processes up).

With 15-ish hours of configuration I have my GitLab hosting my SCM, my CI/CD, all of my static HTML sites, my artifact storage, my Docker registry, and even my documentation (I've almost switched 100% over to using their Web IDE to edit markdown).

I've been running this way for over a year and it's incredibly easy to keep maintained. GitLab's upgrade cycles are some of the smoothest around and are always packed with useful features. Overall I've been self-hosting GitLab for about 7 years - it's one of the best software products I've ever used.

Although I love to shill for them - I have no affiliation with GitLab outside of being an enthusiastic user.

Similar situation for me. But I kept using gitlab.com (I didn't want to maintain anything more than I have to)

At $work-1 I had been managing ~800 github repos with circleCI integrations. I was reluctant to stay on gitlab, especially with the hilarious down times in 2018. Two things kept me on there:

1) the runners

2) the ease of organising repos into projects

Now that the SRE team are up to scratch, I don't think I'd go back to github.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.