Live data from Hacker News

Every software system used at Gitlab

about.gitlab.com

41–50 of 123 posts

Re: Every software system used at Gitlab

#41
post #31

Gitlab has been pretty great so far, but the code review tooling is so poor I think I need to look elsewhere. The pull request pages take forever to load, they can't handle pull requests with over 800 lines well at all. It will collapse files with over 100-200 lines of changes for seemingly no reason (hiding the comments within them). You can't ignore whitespace in diffs, and the comments disappear from the diff if t…

This sounds as it it would be a great improvement over Bitbucket. :-)

Re: Every software system used at Gitlab

#42
post #30

I don't know if any Gitlabbers are in the comments but I'd be interested to know: Is this basically your internal asset register open sourced? I suppose they're not particularly top secret but there could be a version that has some more sensitive data and this is a safe derivative for example. Similarly, such an asset register would likely have non-technical assets as well while this just seems to be tangible, techni…

Err, what is an internal asset register?

Re: Every software system used at Gitlab

#43
post #31

Gitlab has been pretty great so far, but the code review tooling is so poor I think I need to look elsewhere. The pull request pages take forever to load, they can't handle pull requests with over 800 lines well at all. It will collapse files with over 100-200 lines of changes for seemingly no reason (hiding the comments within them). You can't ignore whitespace in diffs, and the comments disappear from the diff if t…

In my experience, if you are reviewing 800+ line PRs you should be in an IDE. I believe the average human being can not review an 800 line diff reliably.

Such large PRs would also probably benefit from live discussions over video (or in the good old days -- in person).

Re: Every software system used at Gitlab

#44
post #39
post #31

Gitlab has been pretty great so far, but the code review tooling is so poor I think I need to look elsewhere. The pull request pages take forever to load, they can't handle pull requests with over 800 lines well at all. It will collapse files with over 100-200 lines of changes for seemingly no reason (hiding the comments within them). You can't ignore whitespace in diffs, and the comments disappear from the diff if t…

Yeah, this is definitely one of GitLab's weakest points at the moment and seriously impacts day-to-day work here as well. Simple features like ticking off files you've already reviewed are missing and even mid-sized MRs are a pain to review even on a beefy machine.

This feature already exists, I use it all the time.

Re: Every software system used at Gitlab

#45

How did GitLab track and create this diagram? Is there a service that does it automatically?

can such a diagram be generated using text markup ? i want to have this in revision control and then generate this in a static page (Nextjs or Gatsbyjs)

It’s a bit clunky, but Graphviz and its DOT language[1] might do the trick.

[1] https://en.m.wikipedia.org/wiki/Graphviz

Re: Every software system used at Gitlab

#46
We've just had a bad experience with GitLab annual renewal, to the point where we didn't know if they'd cancelled our account or not.

The billing accounts system seems to be completely disconnected from user accounts. A notification banner was spammed to users in the GitLab.com user interface, saying that our account was going to be cancelled becuase we didn't have auto-renew. The users who got the banner didn't have permission to act on it in the billing system. The billing system said that we _were_ on track to renew, which disagreed with the banner. Eventually it transpired that the end-of-year "truing up" meant that our account was on hold, but we weren't notified of this.

And when we _did_ pay the bill we get a banner saying "you've been downgraded to the free plan" when the gitlab.com interface says we hadn't.

It really undermined confidence in how well these systems are connected.

On the flip side, the fact that everything is open meant that you can see customer support reps raising internal bugs about this stuff. The principle of open-everything makes it more pallatable, but it doesn't make up for lost confidence.

Re: Every software system used at Gitlab

#47
Wow, I didn't expect so much!

GitLab, here is my proposal: remove 80~90% of this. Keep the essential. Prove that you are a really innovative company. Stop following analytics. Engage with your users.

Prove that you can control entropy and recover your agility rather than going the bureaucratic enterprise software way, just waiting for a more hungry and foolish player to cut the grass under your feet.

Re: Every software system used at Gitlab

#48

We've just had a bad experience with GitLab annual renewal, to the point where we didn't know if they'd cancelled our account or not. The billing accounts system seems to be completely disconnected from user accounts. A notification banner was spammed to users in the GitLab.com user interface, saying that our account was going to be cancelled becuase we didn't have auto-renew. The users who got the banner didn't have…

fault confessed is half redressed

Re: Every software system used at Gitlab

#49

Why is salesforce the center of attention?

Because it is the source of truth for all of your customers both current and future. And surely customers should be the centre of everyone's business.

Like OP, I'd love to understand better what Salesforce does (so well, it seems).

Its a bit hard to imagine, just like SAP software (for me), since all your experience is on industries far from that world.

Re: Every software system used at Gitlab

#50

For a company that makes and promotes FOSS, their tech stack sure is dominated by proprietary SASS vendor lock in solutions.

As someone who has a B2B startup there is almost nothing in the open source space for Marketing/Sales Ops. And anything that does exist is really low quality. And it's because (a) most developers aren't exposed to non-Engineering parts of the company so they have no understanding of what problem to solve and (b) it is incredibly lucrative to build a proprietary SaaS solution.

There is Odoo which can be self-hosted too and has a fairly generous open source edition.
Post reply on HN