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

51–60 of 76 posts

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

#51

Post by szatkus »

awild wrote: post #50
intsunny wrote: post #32

Earlier quoted context omitted.

I suspect due to the sheer number of internal deploys, Gitlab does not always get the exposure warranted. My work place is switching from internal Gitlab/gitlab-runners to external gitlab.com + internal gitlab-runners. We are very happy with both scenarios, but neither gains Gitlab any exposure.

Can you expand on that scenario, how are you hosting the internal runners? Our gitlab server is quite limited in capacity and that would actually be a cool solution to outsource them onto our bigger servers.

You can install gitlab-runner package on your own machine and register the instance in the Gitlab. It will be seen in the Gitlab panel next to all other runners.

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

#52

Post by timdorr »

chenzhekl wrote: post #18

For anyone interested, there‘s a similar CLI for GitHub: https://github.com/cli/cli

There is also the extra helpful hub: https://github.com/github/hub

It is a wrapper around git (you can alias it to the git command) that adds GH-aware things, like checking out a PR by URL or number, or opening up the repo page with `git browse`.

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

#53

Post by StavrosK »

I tried this, and it seems very useful, but there's no documentation and the CLI help command doesn't work. Why make a tool and then not tell anyone how to use it? It's frustrating. No combination of `glab help command` or `glab command --help` works.

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

#54

Post by nonbirithm »

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.

The only reason I choose GitHub over Gitlab is the network effect.

If making someone create a new account on Gitlab means they won't contribute to a project, then I'd rather publish it on GitHub instead, even if GitHub is closed-source. The network of GitHub is intrinsic to that website and Gitlab might not ever be able to replicate the size of its userbase. (Of course, if I'm proven wrong I'd migrate.)

Yes, it doesn't help Gitlab to have this mentality, but out of the dozens of OSS repositories I've used only two have come from Gitlab. Every single other one I had originally found on GitHub.

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

#55

Post by giancarlostoro »

mcintyre1994 wrote: post #49
fileeditview wrote: post #30

Earlier quoted context omitted.

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.

Does this mean when you `git push origin ` it gets pushed to both remotes? I had no idea you could have two remotes with the same name, neat!

TIL that's exactly what this does, alternatively you can add them all to an 'all' remote, to make it more explicit:

https://jigarius.com/blog/multiple-git-remote-repositories#t...

However, you can add multiple URLs to 'origin' and push to them all at once.

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

#56

Post by deepsun »

nonbirithm wrote: post #54
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.

The only reason I choose GitHub over Gitlab is the network effect. If making someone create a new account on Gitlab means they won't contribute to a project, then I'd rather publish it on GitHub instead, even if GitHub is closed-source. The network of GitHub is intrinsic to that website and Gitlab might not ever be able to replicate the size of its userbase. (Of course, if I'm proven wrong I'd migrate.) Yes, it doesn…

Why would they contribute to this project if they don't have a gitlab account?

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

#57

Post by cube2222 »

deepsun wrote: post #56
nonbirithm wrote: post #54

Earlier quoted context omitted.

The only reason I choose GitHub over Gitlab is the network effect. If making someone create a new account on Gitlab means they won't contribute to a project, then I'd rather publish it on GitHub instead, even if GitHub is closed-source. The network of GitHub is intrinsic to that website and Gitlab might not ever be able to replicate the size of its userbase. (Of course, if I'm proven wrong I'd migrate.) Yes, it doesn…

Why would they contribute to this project if they don't have a gitlab account?

They may use self-hosted gitlab at work.

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

#58

Post by akerro »

Already__Taken wrote: post #33
akerro wrote: post #17

Earlier quoted context omitted.

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.

I imagine that's an oversight of sorts because you could just build the images on gitlab too.

There are ways, but:

1. I need to run gitlab ci myself on my host(s)

2. My host must be logged in to docker hub

3. Gitlab CI must run as privileged container

4. There are more hacks required to let gitlabci build the image and push as me.

on github you just authorize docker-hub to get webhooks from github, and that's it, it does the rest itself.

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

#59

Post by akerro »

brodock wrote: post #39
akerro wrote: post #17

Earlier quoted context omitted.

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.

Can't you build and push via CI?

Too lazy to do the setup on multiple computers

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

#60

Post by joshlambert »

ianbooker wrote: post #15
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`.

That was a theory I had: That Unicorn leaks and that Unicorn Killer is not killing any of the workers, since it does so all 160 requests and there are no request happening at the moment. Then I saw the new installation uses Puma ;)

Hi, GitLab product manager here. I'm sorry that we haven't provided a good experience. We try really hard to make sure GitLab deployments "just work", and clearly it does not for either of you.

Both Puma and Unicorn should be killed after they exceed a certain size to avoid this situation from happening. It's possible either this is not working in some situations/configurations, or there is a leak elsewhere although this is the first time I have heard reports of this.

What configuration is being changed from the defaults? Alternatively if you could open an issue with any additional detail we will try to figure out what is happening and fix it: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues

Post reply on HN