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

Gitlab 13.9

about.gitlab.com

Post reply on HN
Print view View original

21–30 of 63 posts

Re: Gitlab 13.9

#21

Post by cmckn »

richardwhiuk wrote: post #5
ducktective wrote: post #3

Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.

IMHO, just use GitLab.com or GitHub.com's personal private repos options.

Agreed; I have pretty limited time to spend on personal projects, so I try to minimize the amount of "infra" I have to maintain. I'm an activist about some things, but running my own git remotes and CI isn't one of them.

Re: Gitlab 13.9

#22

Post by majkinetor »

There are some very nice features in this release:

1. VSCode MR viewing and CI autocomplete of env vars (and in next version adding comments) which finally means I can totally stop using clanky browser GUI for that but people that like it can.

2. PowerShell Core as shell runner on Linux

3. Suggestion in MR like on GH

4. Follow user like on GH

5. Automatic changelog via push tags

6. Recursive view of parent child pipelines (still some murky UI elements tho, like not being able to expand child on parent, something that worked previously). Unfortunately doesn't seem to be working with includes on trigger...

7. Reviewer follow up and viewed items. So far IMO, GH PR was much more pleasurable experience, maybe those 2 features will fix those problems for me - I am not sure if its just some quirk on my standalone or what but on GL I can't really understand what is going on after first review and provided fix. On GH PR, it simply hides changed lines that were previously reported as problematic but not on GL, several times it even didn't show commits that came afterwards. Rebasing also seem to mess the process up. Maybe I am just dumb.

I wish pipelines will get some filtering love, like viewing jobs by name and/or their status. Not really sure why this basic and very important stuff was never implemented. I sometimes have to scan several pages to find last instance of the job I am interested in (note that I use monorepo and each sub-service has its own standalone pipeline and parent triggers only specific ones based on code changes)

Another wish is option to select subset of all possible child pipelines when manually creating pipeline - now it triggers all of them.

Re: Gitlab 13.9

#23

Post by bsder »

qbasic_forever wrote: post #10
kevincox wrote: post #6

Earlier quoted context omitted.

As I see it: GitLab has CI and a whole host of other features (artifact repositories, pages, ...) Gittea is a nice WebUI for viewing source files with simple issue and patch management. bare-git is fine if you don't need any web presence.

Gitea is a lot more than just a web UI. It's a whole multi-tenant platform if you need--it can act as an OAuth2 provider and drive SSO, login, etc. for all kinds of other apps or services. You could even have gitea used as a login/auth for a kubernetes cluster (with dex). It's like gitlab but way less documentation and slightly less polish.

> it can act as an OAuth2 provider and drive SSO, login, etc. for all kinds of other apps or services.

Can I get a link to documentation/discussion on that?

Re: Gitlab 13.9

#24

Post by INTPenis »

ducktective wrote: post #3

Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.

I don't have an answer for you but your question made me think; "why can't other gitlab alternatives use their gitlab runner?"

That shouldn't be hard to do, make a gitea that can use gitlab runners, right? It must be an open protocol.

Re: Gitlab 13.9

#25

Post by kingosticks »

cat199 wrote: post #12
kipari wrote: post #7

Earlier quoted context omitted.

I started out using Gitlab for my personal repos, but have switched to using bare Git repos on a VPS for the last few years. If you won't be collaborating with anyone else, nothing beats being able to just write: ssh $HOST git init --bare repo/foo git remote add origin $HOST:repo/foo

to note, gitolite provides a very simple addition to the 'simple git server over ssh' scenario without much hassle, might be worth looking into for this use case

If it's just you using it, what additions does gitolite bring (genuine question)?

Re: Gitlab 13.9

#26

Post by YorickPeterse »

majkinetor wrote: post #22

There are some very nice features in this release: 1. VSCode MR viewing and CI autocomplete of env vars (and in next version adding comments) which finally means I can totally stop using clanky browser GUI for that but people that like it can. 2. PowerShell Core as shell runner on Linux 3. Suggestion in MR like on GH 4. Follow user like on GH 5. Automatic changelog via push tags 6. Recursive view of parent child pipe…

> Automatic changelog via push tags

Worth mentioning: we don't support generating changelogs when pushing tags. What we did add is an API that can be used to generate changelogs. This API takes a range of commits to use for the changelog. What we support here related to tags is automatically using the tag of the last release as the start of this range.

Re: Gitlab 13.9

#27

Post by Aeolun »

ducktective wrote: post #3

Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.

Gitlab is not terribly resource hungry? And not very latency sensitive either, so you can put it wherever you get the cheapest/best hosting.

Re: Gitlab 13.9

#28

Post by [deleted] »

kipari wrote: post #7
ducktective wrote: post #3

Between Gitlab,Gitea and bare-git repos, which one should I use for personal (1-man) projects? Here are my thoughts: Gitlab is resource-hungry but provides CI solutions and is kind of a setup-once-then-forget solution. Gitea is light weight but for any additional functionality third-party utilities are needed.

I started out using Gitlab for my personal repos, but have switched to using bare Git repos on a VPS for the last few years. If you won't be collaborating with anyone else, nothing beats being able to just write: ssh $HOST git init --bare repo/foo git remote add origin $HOST:repo/foo

[deleted]

Re: Gitlab 13.9

#29

Post by Aeolun »

cmckn wrote: post #21
richardwhiuk wrote: post #5

Earlier quoted context omitted.

IMHO, just use GitLab.com or GitHub.com's personal private repos options.

Agreed; I have pretty limited time to spend on personal projects, so I try to minimize the amount of "infra" I have to maintain. I'm an activist about some things, but running my own git remotes and CI isn't one of them.

Running my own git remotes and infra is my personal project ;)

Re: Gitlab 13.9

#30

Post by qbasic_forever »

bsder wrote: post #23
qbasic_forever wrote: post #10

Earlier quoted context omitted.

Gitea is a lot more than just a web UI. It's a whole multi-tenant platform if you need--it can act as an OAuth2 provider and drive SSO, login, etc. for all kinds of other apps or services. You could even have gitea used as a login/auth for a kubernetes cluster (with dex). It's like gitlab but way less documentation and slightly less polish.

> it can act as an OAuth2 provider and drive SSO, login, etc. for all kinds of other apps or services. Can I get a link to documentation/discussion on that?

OAuth2 provider config: https://docs.gitea.io/en-us/oauth2-provider/

For dex (k8s auth), specifically: https://dexidp.io/docs/connectors/gitea/

Hooking it up to do SSO for other OAuth/OIDC apps is pretty similar. For something that doesn't do OAuth you could use vouch proxy in front of it and get SSO: https://github.com/vouch/vouch-proxy/issues/203

It's really slick and fun to throw gitea on a cheap VPS, then a few apps like drone CI, a k3s kubernetes cluster, etc. and have it all just interoperate and auth together seamlessly. I won't lie though it's an enormous amount of annoying and badly documented work to get it all together.

Post reply on HN