Gitlab 13.1 • Hacker News Board

Re: Gitlab 13.1

#71

Post by dan1234 » Tue, Jun 23, 2020, 8:04 AM UTC

sytse wrote: post #57

dan1234 wrote: post #33

Looks like WebAuthn is still missing, even though there seem to have been merge requests featuring it forever! Anyone know which milestone it’ll be merged into?

This relevant MR https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26692 is scheduled (not guarateed) for 13.2 (July 22, 2020). Also see this issue https://gitlab.com/gitlab-org/gitlab/-/issues/22506

Thanks for the update, I’ve looking forward to this feature for around 6 months!

Re: Gitlab 13.1

#72

Post by [deleted] » Tue, Jun 23, 2020, 8:44 AM UTC

efiecho wrote: post #69

citrus1330 wrote: post #21

I love GitLab Better UI than GitHub and was first to provide free private repos

> Better UI than GitHub I think that GitHub has a much better UI than GitLab. GitLab is slow and bloated compared to GitHub. Requiring Javascript for browsing the code repository is just bad design.

[deleted]

Re: Gitlab 13.1

#73

Post by elmolino89 » Tue, Jun 23, 2020, 8:58 AM UTC

Version control for GitLab wiki is still not there. Supposedly it will be in 13.2.

For a small shop using GitLab local install versioning of the systems/software/lab protocols documentation is something hard to live without.

Re: Gitlab 13.1

#74

Post by samdbeckham » Tue, Jun 23, 2020, 9:47 AM UTC

efiecho wrote: post #69

citrus1330 wrote: post #21

I love GitLab Better UI than GitHub and was first to provide free private repos

> Better UI than GitHub I think that GitHub has a much better UI than GitLab. GitLab is slow and bloated compared to GitHub. Requiring Javascript for browsing the code repository is just bad design.

GitLab employee here. As much as it pains me, I have to agree with you for the most part. Performance is one of the biggest pain points for our frontend team, but is something we're actively working on.

Here's one of our epics to show our progress: https://gitlab.com/groups/gitlab-org/-/epics/716

We're in the process of migrating parts of our codebase from haml templates to Vue apps, which does have the unfortunate downside of requiring javascript to run. We're looking into solving this with server side rendering, but it's early days right now.

Here's the issue for that: https://gitlab.com/gitlab-org/gitlab/-/issues/215365

If either of these things are things you could help with, we encourage you to contribute and help us make GitLab a better place.

Re: Gitlab 13.1

#75

Post by lokedhs » Tue, Jun 23, 2020, 10:49 AM UTC

stock_toaster wrote: post #37

jtwaleson wrote: post #35

I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any ot…

> I think any giant company would have a hard time integrating all-remote Gitlab. Atlassian maybe? ( shudder )

If we are thinking less-than-ideal buyers, I could imagine Oracle or SAP could be interested?

Re: Gitlab 13.1

#76

Post by yters » Tue, Jun 23, 2020, 11:04 AM UTC

mdaniel wrote: post #65

yters wrote: post #61

What makes Gitlab significantly better than the other gitlings?

IMHO, it's integration. znpy was correct, but incomplete: GitLab ships with CI/CD, secrets management via Vault, AWS ECS integration, Kubernetes integration, issue tracking, wiki, an artifact repository for 5 major package types, metrics, alerts, and even a full-blown Slack competitor (optional, of course) You can absolutely integrate your favorite, and/or best of breed, tools with any git hosting software that you'd…

does it make sense to switch to gitlab if one already has most of those things integrated?

Re: Gitlab 13.1

#77

Post by yters » Tue, Jun 23, 2020, 11:05 AM UTC

znpy wrote: post #63

yters wrote: post #61

What makes Gitlab significantly better than the other gitlings?

the gitlab-ci is the killer app. also, the fact that you can self-host it and it's very easy to do so.

how is that better than jenkins?

Re: Gitlab 13.1

#78

Post by jsilence » Tue, Jun 23, 2020, 11:43 AM UTC

jtwaleson wrote: post #35

I somehow had a feeling Gitlab would be bought this year, but the list dramatically falls apart upon closer inspection: - Google: will never work, completely different mindset and engineering culture. Gitlab feels way too unrefined (in a good sense). - AWS: Gitlab is already too different from their tech, and will never be that tightly coupled with the rest of AWS. - IBM: :') they wish - MS: already has GitHub Any ot…

Facebook? duck

Re: Gitlab 13.1

#79

Post by boleary-gl » Tue, Jun 23, 2020, 12:27 PM UTC

Earwig wrote: post #15

boleary-gl wrote: post #6

Earlier quoted context omitted.

GitLab technical evangelist here. I can't seem to reproduce this - maybe it's uBlock Origin? Are you sure it's the default configuration? What were the requests to - just to the main HTML page?

Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help.

We're working on this issue here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052. Hardest part - like much of software engineering - is trying to figure out how to reproduce it.

Re: Gitlab 13.1

#80

Post by YorickPeterse » Tue, Jun 23, 2020, 1:36 PM UTC

rossmohax wrote: post #20

threeseed wrote: post #11

It's great and impressive how quick Gitlab moves in adding new features. But if I have a Graphic Design repo it emphasises Kubernetes, Packages and Security features that have zero relevance. And there is no way to disable them. And that on every single repo it places these Add License/Contributors etc buttons front and centre even though for 99% of internal projects they serve no purpose. Every release Gitlab seriou…

> It's great and impressive how quick Gitlab moves in adding new features. Don't trust their feature list, they often "forget" to use it themselves. Many of those features are there to tick the box and daze executives, but are barely usable in practice. It took them a year to start supporting Kubernetes clusters with RBAC, they didn't use autodevops for their own releases, even for simple components, nor any kubernet…

We've actually been using feature flags for quite a while for some release tooling related projects. Geo has been used in the past when we migrated to Google Cloud if I remember correctly.