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

31–40 of 63 posts

Re: Gitlab 13.9

#31

Post by qbasic_forever »

xtracto wrote: post #15
qbasic_forever wrote: post #9

Earlier quoted context omitted.

bare repo synced up to S3 is my vote, with end to end encryption enabled. Why give some third party access to your data if you don't need to?

S3 is a 3rd party for most people.

Yes, hence the end to end encryption: https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingC... Once enabled as far as amazon is concerned your bucket is an entirely random bag of bits, they have no idea what's inside or how to access it. Even if compelled by a state government amazon can't give up your data in any usable form without your encryption keys.

Re: Gitlab 13.9

#32

Post by sdfhbdf »

Very welcome improvements in Code Review department. Really like the explicit Viewed checkbox (even though I noticed that the bolding in the sidebar with the file tree tried to solve the same problem) and really nice with the suggestions.

My two top wishlist leftover items in that regard are

1. Marking whether a comment requests changes or not. This is of course straight out of GitHub, but I think their flow better matches what I found to be happening a in a lot of changes. I see such states for a Code review of a MR: Changes approved, Reviewer requests changes, reviewer leaves feedback (like "nice implementation", "good refactor", "minor: maybe you can refactor this?"). The last one is the most blurry in the GitLab approach since the way we can solve it is by starting a comment thread that is not resolved and approving a MR at the same time but it feels clunky. Maybe they can take a page out of GitHub's book.

2. Personal slack notifications. I would love to have first-party support for the notification system around MR, MR Comments, Being assigned, pipeline failing that messages me privately on slack. Jira recently had a revamp in their slack app and all notification moved there and overall I welcomed these changes since the only other way it seems to be email which speaks for itself - limited interactivity and it's becoming less of a notification medium anyway. [1]

[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/17958

Re: Gitlab 13.9

#33

Post by kingosticks »

cat199 wrote: post #13
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.

> bare-git is fine if you don't need any web presence. cgit or gitweb can be nice additions to bare git for simple repository browsing without the full 'project managment' aspects that gitlab/gitea/redmine etc. add

Are there any nicer interfaces for gitweb? The basic functionality (just browsing a repo) is perfect but it's not the prettiest.

Edit: this looks like what I mean, just so happens to be github style but that's not a requirement! https://github.com/kogakure/gitweb-theme

Re: Gitlab 13.9

#34

Post by tenaciousDaniel »

john_cogs wrote: post #2

GitLab team member here. One thing that stood out to me in this release is the strength of contributions from the wider GitLab community. Among the 299 community contributions in this release: - GPU and smart scheduling support for GitLab Runner [1] - The ability to follow other GitLab users [2] - 1 line installer for the GitLab Kubernetes Agent [3] - An activity filter on Vulnerability Reports [4] 1 - https://about.…

Awesome!

A small thing I'd love to see - the ability to collapse all files in a merge request. Right now the only option is to expand all. We have a lot of generated test files and it nearly crashes the browser when they're all open. Right now I have to collapse each one individually, sometimes dozens of files.

Re: Gitlab 13.9

#35

Post by PurpleFoxy »

Aeolun wrote: post #27
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.

It requires quite a lot of memory since it’s a massive rails app.

Re: Gitlab 13.9

#36

Post by john_cogs »

tenaciousDaniel wrote: post #34
john_cogs wrote: post #2

GitLab team member here. One thing that stood out to me in this release is the strength of contributions from the wider GitLab community. Among the 299 community contributions in this release: - GPU and smart scheduling support for GitLab Runner [1] - The ability to follow other GitLab users [2] - 1 line installer for the GitLab Kubernetes Agent [3] - An activity filter on Vulnerability Reports [4] 1 - https://about.…

Awesome! A small thing I'd love to see - the ability to collapse all files in a merge request. Right now the only option is to expand all. We have a lot of generated test files and it nearly crashes the browser when they're all open. Right now I have to collapse each one individually, sometimes dozens of files.

Have you tried enabling "Show one file at a time on merge request’s Changes tab"? That might help.

https://docs.gitlab.com/ee/user/project/merge_requests/revie...

Re: Gitlab 13.9

#37

Post by salzig »

INTPenis wrote: post #24
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.

interesting thought, isn't gitlab-ci-runner only pulling jobs to be executed and then pushes back logs? shouldn't be that hard to implement.

Re: Gitlab 13.9

#38

Post by Normal_gaussian »

tenaciousDaniel wrote: post #34
john_cogs wrote: post #2

GitLab team member here. One thing that stood out to me in this release is the strength of contributions from the wider GitLab community. Among the 299 community contributions in this release: - GPU and smart scheduling support for GitLab Runner [1] - The ability to follow other GitLab users [2] - 1 line installer for the GitLab Kubernetes Agent [3] - An activity filter on Vulnerability Reports [4] 1 - https://about.…

Awesome! A small thing I'd love to see - the ability to collapse all files in a merge request. Right now the only option is to expand all. We have a lot of generated test files and it nearly crashes the browser when they're all open. Right now I have to collapse each one individually, sometimes dozens of files.

Mark them linguist-generated in .gitattributes. GitLab will show them as changed but not show the diff.

Re: Gitlab 13.9

#39

Post by weitzj »

I have to use GitLab. But I really quite don’t get some features like:

Multiple published html pages per job. Seems not possible: You have to have a special job name “pages” and your build artifacts have to be in a special directory “public” in order for this job to work correctly.

Also collecting test coverage reports by grepping with a regex through your build stdout feels weird.

These 2 examples leave a weird feeling - a feeling that some easily applicable features are just bolted onto GitLab and the underlying architecture is not capable of incorporating these features an a better way (multiple html websites, specialized coverage report parsers).

Also extended/sharing pipelines between multiple teams without duplicating code or having stages “leaking into teams code” feels weird.

Re: Gitlab 13.9

#40

Post by cmckn »

Aeolun wrote: post #29
cmckn wrote: post #21

Earlier quoted context omitted.

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 ;)

Godspeed! I tried deploying gitlab on my k8s cluster at home and ran screaming after an hour or so haha
Post reply on HN