s/This website uses cookies/This website got mugu'd by European policymakers/
Every software system used at Gitlab
61–70 of 123 posts
Re: Every software system used at Gitlab
#62Gitlab 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…
I don’t understand. This describes basically every code review tool I’ve ever used. If there’s something aside from Gitlab that I should try that still integrates, I’d love to know.
Re: Every software system used at Gitlab
#63I 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?
An asset register is how companies keep track of their assets. Any software license, computer, monitor, keyboard, copy machine, etc. the company claims as an asset is tracked in the register.
Re: Every software system used at Gitlab
#64Nice, just curious counting the filled and dotted lines - how this software is integrated together?
Re: Every software system used at Gitlab
#65Surprisingly, does not look too messy
Re: Every software system used at Gitlab
#66Earlier quoted context omitted.
Because this is the Business Operations tech stack.
Correct! If someone is more interested in what GitLab itself consists of please see https://docs.gitlab.com/ee/development/architecture.html#com...
The diagrams are nice, but it would be so much better if the nodes were linked to documentation.
Re: Every software system used at Gitlab
#67Gitlab 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…
I don’t understand. This describes basically every code review tool I’ve ever used. If there’s something aside from Gitlab that I should try that still integrates, I’d love to know.
For huge diffs, there’s not much that beats `git checkout && git diff HEAD^`.
For leaving comments, pretty much every system I’ve used has issues. At work we use phabricator; the default settings are atrocious but they can be tuned to something workable.
I sometimes wonder how hard it would be to get diff reviews to be a first (or even second) class citizen of the git ecosystem. That way you can finally get the bliss of leaving review comments in the IDE. They already have “notes” which are vaguely similar, maybe it’s something they’re considering?
Re: Every software system used at Gitlab
#68We'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…
Sorry that this happened. We still have a long way to go to improve our billing system. We have allocated more people to it since a few months and are making much faster progress. But it isn’t we’re it should be at the moment.
Re: Every software system used at Gitlab
#69Earlier quoted context omitted.
This feature already exists, I use it all the time.
In GitLab? Maybe we're using an outdated GitLab version here, but I can't find it. And it doesn't seem to be mentioned in the offical Reviewing documentation: https://docs.gitlab.com/ce/user/project/merge_requests/revie... If you mean the "collapsing" feature, this is really not equivalent, since the state does not persist between multiple review sessions.
I don't have it either. I wish we could "check" things off.
I also wish I had more ability to do settings "by group", rather than by project.
Re: Every software system used at Gitlab
#70Is Salesforce still a big things?
Gigantic and for dev jobs it pays extremely well for easy work.