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

Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

github.com

Post reply on HN
Print view View original

21–30 of 76 posts

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#21

Post by mosselman »

akerro wrote: post #17
mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I maintain a bunch of docker images that are purposed to run on gitlab ci, they are obviously hosted on github because only github has push-event integrations with docker hub. I make a push, docker hub builds and publishes the image, the image is only pulled by gitlab ci. Gitlab is great, but it lacks many popular integrations that must come from not-gitlab.

Good point. I just thought it was funny, but it is good to know that there ARE differences other than branding.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#22

Post by [deleted] »

akerro wrote: post #17
mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I maintain a bunch of docker images that are purposed to run on gitlab ci, they are obviously hosted on github because only github has push-event integrations with docker hub. I make a push, docker hub builds and publishes the image, the image is only pulled by gitlab ci. Gitlab is great, but it lacks many popular integrations that must come from not-gitlab.

[deleted]

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#24

Post by Jugurtha »

lbotos wrote: post #9
Jugurtha wrote: post #7

Earlier quoted context omitted.

I have somewhat similar experience. I have 16GB of RAM, 12 CPU. You can reduce the number of unicorn workers in `config/gitlab.rb`.

what are you seeing in the logs? OOM-killer? Also, newer versions use Puma which lower RAM needs if you are seeing Unicorn OOM Killer

Ah, my bad. I have `12.10.6 (833223f2a7f)`. Time to pull, as it really hogged my RAM. The pattern is that it will periodically consume much more resources.

Thanks for the heads-up.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#25

Post by toastal »

P4wl0w wrote: post #6
kanobo wrote: post #3

Earlier quoted context omitted.

Hugely ironic, but not surprising since projects on GitHub get better exposure and also the ability to raise funds with GitHub sponsors.

This is true and important. But I also have to admit that I like the interface of GH more and I am just used to searching on GH - it always has been like google search for code for me.

GitLab has a dark theme though

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#27

Post by hobo_mark »

gru wrote: post #8
mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I have created a small tool that automatically mirrors public repos from GitLab to GitHub: https://github.com/grdl/gitlab-mirror-maker Meaning, a repo can be hosted on GL but still benefit from better exposure and disoverability of GH.

But GitLab already has repo mirroring built-in, what am I missing?

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#28

Post by remexre »

techntoke wrote: post #23

Anyone else switched entirely to Tekton or another CI/CD platform because GitLab feels like a bloated monolith and too centralized at this point?

sr.ht for me -- being able to ssh into failed builds' vms is super-duper nice

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#29

Post by hardwaresofton »

ianbooker wrote: post #4

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours. The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off. Afterwards I reconfigure various config lines and repeat.

Don't want to be that guy, but containerization (gitlab omnibus[0]) might actually help you in this case -- in particular the resource utilization caps that you can get with linux containers. While I can't tell you why Gitlab CE is crashing for you, it is much less likely to take down the entire machine from inside a resource-constrained container, and it will probably force you to make the configuration a bit more reproducable as well (and maybe that will help twiddling).

Would love to read about the actual config issues you're having and how you're solving them one by one -- are you writing about it anywhere?

[0]: https://docs.gitlab.com/omnibus/docker/README.html

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#30

Post by fileeditview »

gru wrote: post #8
mosselman wrote: post #2

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I have created a small tool that automatically mirrors public repos from GitLab to GitHub: https://github.com/grdl/gitlab-mirror-maker Meaning, a repo can be hosted on GL but still benefit from better exposure and disoverability of GH.

How I usually do it if I want to have my project on Github and Gitlab is configure two push remotes like this:

> git remote set-url --add --push origin

> git remote set-url --add --push origin

This way I have an automatic backup to the second remote.

Post reply on HN