Live data from Hacker News

GitLab 8.5 released

about.gitlab.com

231–240 of 246 posts

Re: GitLab 8.5 released

#231

Earlier quoted context omitted.

You'd be in the minority. Correct me if I'm wrong, but I'd bet you're at a small company where a low-level employee's opinion was taken into account when making the decision of which product to use for 10-50 people. In medium to large sized companies, Atlassian will usually win out when you have a CTO that manages 100+ developers. Enterprises really like to stick with the "safe bet", where there are expensive license…

I've used plenty of other options- we even ran an internal GitLab instance prior to moving to BitBucket at my last company. Atlassian's suite of products are a safe bet because they're generally good products. I like the GitLab feature set more than BitBucket but when I went started my own company it was generally cheaper for my team of 5-8 to use hosted JIRA, BitBucket, and Confluence then it would be for me to pay…

Great to hear you're using JIRA, Bitbucket and Confluence together. How is the integration between the tools? It's definitely a use case we're hearing more often where teams need more than just storing and working on code.

Re: GitLab 8.5 released

#232

Earlier quoted context omitted.

Yep. I got my work to purchase EE license for Gitlab because it's miles ahead of Bitbucket Server.

Would love to hear what features in your opinion but Gitlab miles ahead of Bitbucket Server.

We tested Bitbucket Server when it was still called Stash, and compared it to Gitlab at the time.

- Merge requests/code review in Gitlab is much better, whereas with Atlassian they recommend purchasing another product

- Integrated Wiki, whereas Atlassian they recommended Confluence

- The UI is absolutely terrible, even now the Bitbucket front-page where it dumps you when logged in is a disorganised mess and I can never find what I am looking for

- Speed, Gitlab running on my own server is MUCH faster, compared to Stash

- There was no way to easily add code snippets to be shared with the rest of the team, ala Snippets.

- Integration with the rest of the Atlassian toolset was so-so, and left a lot to be desired honestly.

- Statistics and information about the code and who is contributing and everything along those lines, makes for pretty graphs that make higher ups happy.

- Bitbucket doesn't currently have a view within the web interface for how many commits have been made to a project. People like numbers, and watching them grow!

- I have to reiterate, the UI is absolutely terrible in Bitbucket/Stash.

And the real killer is that I can get Gitlab CE and never pay you guys a dime, I've in the past helped out in the Github issues with debugging, and I can be part of the community. The only feature from EE that I need is the ability to use LDAP groups to define what users can and can't access various repositories, and the company I work for can afford to help pay for Gitlab's future to stick around!

Re: GitLab 8.5 released

#233
post #141

Earlier quoted context omitted.

Having used both there's more than enough in either that's bad to justify a switch to the other if you really want to. I personally prefer github's warts to gitlab's. In particular, I find that general site navigation on gitlab is quite tedious and it rarely centres useful information first. But that is very much a qualitative and not a quantitative complaint. The main thing I find extra useful on gitlab is the abili…

Glad you like our WIP function. Do you maybe have any suggestions how we can make navigation better and/or examples of pages where you are missing information?

The decision of what does and doesn't go in the sidebar is very non-intuitive (sometimes what I want is in the sidebar but sometimes it's in the main page). For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar? And then the ordering is also a bit weird -- I don't think many people would consider the order in GitLab to be "in order of importance" or even "regular use". And why can't I see the set of files in the repo when I first open it? This is something I feel GitHub does better -- things are much faster to access and IMO much more intuitive.

Re: GitLab 8.5 released

#234

Earlier quoted context omitted.

I've used plenty of other options- we even ran an internal GitLab instance prior to moving to BitBucket at my last company. Atlassian's suite of products are a safe bet because they're generally good products. I like the GitLab feature set more than BitBucket but when I went started my own company it was generally cheaper for my team of 5-8 to use hosted JIRA, BitBucket, and Confluence then it would be for me to pay…

Great to hear you're using JIRA, Bitbucket and Confluence together. How is the integration between the tools? It's definitely a use case we're hearing more often where teams need more than just storing and working on code.

They're getting better. BitBucket and JIRA work together quite well. With "Smart Commits" in the JIRA hosted version that allow us to move a ticket's status, comment on it, log time, or just show activity towards a ticket via Git commit messages. I use the heck out of it and the team is following quickly behind.

JIRA follows the feature branching workflow pretty well, so if you branch from dev/master with the ticket number as the start of the branch name you can click through to that branch straight from JIRA, which is generally pretty nice.

Confluence isn't nearly as tightly integrated with either. There are some reports, widgets, and stuff you can grab out of JIRA and make some dashboard type reports. Nothing special- we use Confluence to document architecture, deployment procedures, etc. We're definitely not Confluence power users.

Re: GitLab 8.5 released

#235
post #233
post #141

Earlier quoted context omitted.

Glad you like our WIP function. Do you maybe have any suggestions how we can make navigation better and/or examples of pages where you are missing information?

The decision of what does and doesn't go in the sidebar is very non-intuitive (sometimes what I want is in the sidebar but sometimes it's in the main page). For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar? And then the ordering is also a bit weird -- I don't think many people…

Thanks, I've asked our UX engineer to look into this.

Re: GitLab 8.5 released

#236
post #235
post #233

Earlier quoted context omitted.

The decision of what does and doesn't go in the sidebar is very non-intuitive (sometimes what I want is in the sidebar but sometimes it's in the main page). For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar? And then the ordering is also a bit weird -- I don't think many people…

Thanks, I've asked our UX engineer to look into this.

[deleted]

Re: GitLab 8.5 released

#237
post #233
post #141

Earlier quoted context omitted.

Glad you like our WIP function. Do you maybe have any suggestions how we can make navigation better and/or examples of pages where you are missing information?

The decision of what does and doesn't go in the sidebar is very non-intuitive (sometimes what I want is in the sidebar but sometimes it's in the main page). For example, in groups and user profiles you can find the list of projects in the main body of the page (and it's not visible immediately). Why is it not in the sidebar if you have a sidebar? And then the ordering is also a bit weird -- I don't think many people…

Thank you for your feedback, we aware about these issues and already working on improvements on our side, stay tuned!

Re: GitLab 8.5 released

#238

Earlier quoted context omitted.

You'd be in the minority. Correct me if I'm wrong, but I'd bet you're at a small company where a low-level employee's opinion was taken into account when making the decision of which product to use for 10-50 people. In medium to large sized companies, Atlassian will usually win out when you have a CTO that manages 100+ developers. Enterprises really like to stick with the "safe bet", where there are expensive license…

It's so funny that this is the way it's become, as Atlassian grew up being the cheaper, simpler alternative to extremely expensive, super opaque, ultra closed source systems like Clear Case. I remember a time when Atlassian actually raised the prices of Jira's top level of support and service because enterprise CTOs were confused by such a low price point.

Ten years ago I made exactly this migration for a SaaS shop's helpdesk & dev team. At the time JIRA was easily the best value & most customisable solution for integrated ticket tracking. I learned Java & Groovy to write extensions for it. It wasn't just CTO/CIO friendly, JIRA really was the great choice at the time in both UX and ease of implementation. Especially if you'd been bogged down hacking RT or GNATS or permanently scarred by anything from Rational.

What I realised is that eventually they're all ad-hoc, informally-specified, bug-ridden, slow implementation of a workflow engine and metadata service. Your choice is mainly of the interface and domain-specific layering violations.

Troll-friendly soundbite: Atlassian is the new Rational.

Re: GitLab 8.5 released

#239

Earlier quoted context omitted.

It's so funny that this is the way it's become, as Atlassian grew up being the cheaper, simpler alternative to extremely expensive, super opaque, ultra closed source systems like Clear Case. I remember a time when Atlassian actually raised the prices of Jira's top level of support and service because enterprise CTOs were confused by such a low price point.

Ten years ago I made exactly this migration for a SaaS shop's helpdesk & dev team. At the time JIRA was easily the best value & most customisable solution for integrated ticket tracking. I learned Java & Groovy to write extensions for it. It wasn't just CTO/CIO friendly, JIRA really was the great choice at the time in both UX and ease of implementation. Especially if you'd been bogged down hacking RT or GNATS or perm…

"You either die a hero, or live long enough to see yourself become the villain"

Let us know anything specific you'd have us improve - love to know what changed over the last 10 years to make you change your mind.

Re: GitLab 8.5 released

#240
post #142

Earlier quoted context omitted.

GitLab has a ton of strengths, but still has large weaknesses in the area: gitlab.com implementation and design. gitlab.com is the public 'demo' version which people compare to github. It's missing a few key items that would make it appealing to open source developers (and that I'd like to see them prioritize.) E.g.: * Site search. It's been broken for months or possibly years. (Response time > 45 secs., Relevancy is…

I agree we can do a lot better in project discovery on GitLab.com. I do want to mention that https://gitlab.com/explore?utf8=%E2%9C%93&filter_projects=gi... gives results in a few seconds and GitLab itself is the first hit.

Issue search has a lot of room for improvement. All terms in the search query must occur consecutively.
Post reply on HN