Live data from Hacker News

CircleCI Announces Support for Gitlab

circleci.com

81–90 of 124 posts

Re: CircleCI Announces Support for Gitlab

#81
post #56

As an ex-CircleCI employee, this is really exciting because it marks a pretty significant milestone in a particular internal effort. Very much looking forward to what comes after this. This might strike some as a weird event (Gitlab already has CI/CD!), but it _was_ highly requested and is (probably) of other similar things coming to fruition!

+1, also ex-CircleCI employee.

(high-five!)

Re: CircleCI Announces Support for Gitlab

#82
post #78
post #77

Earlier quoted context omitted.

Yeah this is a pain point for me as well, especially when developing the pipelines themselves. There's no good way to run it on my own machine, so I'm stuck pushing new commits to Gitlab over and over again and waiting for it to complete, or rather fail so I can troubleshoot the new error.

Depending on one's definition of "good," running GL locally in docker is (in my experience) painless, given sufficient disk space and probably RAM But yes, your observation is my whole complaint: it is not _reasonable_ to ask a GLCI developer to run a local copy of GL, complete with any shared GLCI template repos, in a local docker container just to have local execution. Maybe I wouldn't complain about it so much had…

unfortunately `act` is pretty bad :(

My go to workflow for workflows (ha) is forking a repo as a private fork and toying on it until I'm happy with the results

Re: CircleCI Announces Support for Gitlab

#83
post #55
post #41

Earlier quoted context omitted.

Gitlab advocates for paying local salaries. That’s actually against my “philosophy“ as you put it, as it is against my direct interest, being a non-US based software developer. Their way to promote remote work is, ironically, hurtful to my prospects as a remote worker.

Overpaying remote workers compared to the local market is bad as it create distortion of local markets (on housing especially where local non remote workers cannot afford living where they work). (I'm a remote worker outside of the US and my personal interest would be to be paid more, but I don't believe it would be the general interest)

Take the extra cash and go on to invest in new housing?

Re: CircleCI Announces Support for Gitlab

#84

Earlier quoted context omitted.

Quick question, why does every startup on earth have google as a customer? Shouldn't a company of this size have its own solutions and programs? This is in no way a deg against your project, its just a general question .

I imagine non-core-product teams at Google are encouraged to submit purchase requests for any tools they think would improve their processes instead of being constrained to existing solutions. They also could just be showing it because someone with an @google.com has a paid account, but I don't know for sure :)

I would think that it also brings the advantage of having tried the actual product in their own ecosystem, Google have a good overall insight into it in case they want to buy it - not sure if this is actually the case though.

Re: CircleCI Announces Support for Gitlab

#85
post #77
post #46

Earlier quoted context omitted.

> a local execution story I can see how "local" can have multiple meanings, but here I meant "as a developer on my laptop, can I have local docker run things the way GL is going to run things?" I hear people say a lot "oh, I just use shell scripts, NBD" but as I said, I'm sure for hello-world setups which don't have any includes or take advantage of GLCI constructs that can work fine, but what rubs me the wrong way i…

Yeah this is a pain point for me as well, especially when developing the pipelines themselves. There's no good way to run it on my own machine, so I'm stuck pushing new commits to Gitlab over and over again and waiting for it to complete, or rather fail so I can troubleshoot the new error.

This thread makes me wonder if the root of the problem is actually the lack of a local runner. I hypothesize that it's the length of the feedback loop that's the real issue.

Even if we had a local runner, if it takes a ton of time to start and complete every step, it'd be almost as painful to debug as a remote runner taking the same time. On the other hand, if the cloud runner is ridiculously fast, and completes steps on the order of single digit seconds, it would be fairly painless to debug.

Re: CircleCI Announces Support for Gitlab

#86
post #55

Earlier quoted context omitted.

Overpaying remote workers compared to the local market is bad as it create distortion of local markets (on housing especially where local non remote workers cannot afford living where they work). (I'm a remote worker outside of the US and my personal interest would be to be paid more, but I don't believe it would be the general interest)

This seems like a variation on the fixed pie fallacy. It's absolutely in the general interest for more people to get paid more. How do you expect poorer markets to catch up with richer ones if you believe that it is bad for people in such markets to get paid more? Nonsense.

It's much easier to catch up if you can compete on price to start with. Why would a company take a chance on a developer in a new location if they've got to pay just as much? Once there's a critical mass of employers hiring in my location, competition will raise salaries up to parity, but sharing the surplus is what incentivises that competition in the first place.

Re: CircleCI Announces Support for Gitlab

#87
post #41
post #30

Earlier quoted context omitted.

That's fair, but I think Gitlab promotes it more strongly. They're 100% remote, and they publish guides teaching other companies how to replicate their remote-first setup: https://about.gitlab.com/company/culture/all-remote/guide/

Gitlab advocates for paying local salaries. That’s actually against my “philosophy“ as you put it, as it is against my direct interest, being a non-US based software developer. Their way to promote remote work is, ironically, hurtful to my prospects as a remote worker.

IMO it's better for our long-term interest if companies can pay what the market will bear. For now splitting the surplus is win-win; as remote work takes off then there wil be more competition and salaries will rise. Growing the pie is better than asking SV employers to overpay on some point of principle.

Re: CircleCI Announces Support for Gitlab

#88

Earlier quoted context omitted.

Related, GitHub has had 'use more powerful hosted runners' in the pipeline for over 2 years[0]. This issue replaced another now-deleted issue[1] from July 2020. Really disappointing, as I've had to resort to using `az vm start` -> run -> `az vm deallocate` to use an on-demand powerful runner. 0: https://github.com/github/roadmap/issues/161 1: https://github.com/github/roadmap/issues/95 (note: added `ga` `ae` and remo…

I'm a bit biased as one of the founders of BuildJet, but we solve this exact issue. BuildJet for GitHub Actions, plugs elegantly into GitHub Actions. With 1-line change in your config, you get 2x speed for half of GitHub's price. Check it out @ https://buildjet.com/for-github-actions

We recently started using buildjet, and it has been nothing short of awesome. So I can highly recommend them.

Re: CircleCI Announces Support for Gitlab

#90
post #46

Earlier quoted context omitted.

We provision our self-hosted runners via Terraform and GitLab's Helm chart. It's a relatively painless setup, but obviously not a few button clicks and commands

> a local execution story I can see how "local" can have multiple meanings, but here I meant "as a developer on my laptop, can I have local docker run things the way GL is going to run things?" I hear people say a lot "oh, I just use shell scripts, NBD" but as I said, I'm sure for hello-world setups which don't have any includes or take advantage of GLCI constructs that can work fine, but what rubs me the wrong way i…

Ah, I see what you're saying. I've had to do some debugging in GitLab instead of local and it wasn't ideal. To prevent mucking with important stuff, I have a scratch project that's dedicated to testing things. It isn't perfect, but I've been able to replicate nearly every problem in the scratch project
Post reply on HN