4 ms·

I'm sorry to hear you're workflow crushing bugs on updates. We'll certainly use the money to hire more developers and service engineers https://about.gitlab.com

by sytse 11y ago

I'm sorry to hear you're workflow crushing bugs on updates. We'll certainly use the money to hire more developers and service engineers https://about.gitlab.com/jobs/ https://about.gitlab.com/jobs/ Although GitLab moves very fast and there always are regressions I thought we are getting much better at releasing patches for all regressions. I'm sorry to hear your experience is different. How large is your repo? Code search shells out to git and that should be very performant. Are the repositories stored the same server as the application runs on? Syntax highlighting switched from pygments to rouge, ensuring we don't have to ship Python anymore. I didn't hear about the problem of assigning the MR, can you link to an issue for that? We want GitLab to work flawlessly when you upgrade. And at the end of each monthly release cycle the patched version should not contain any known problems. We're working hard in the regression issues to make it so https://gitlab.com/gitlab-org/gitlab-ce/issues/1990 https://gitlab.com/gitlab-org/gitlab-ce/issues/1990 and https://gitlab.com/gitlab-org/gitlab-ce/issues/2297 https://gitlab.com/gitlab-org/gitlab-ce/issues/2297 We think that the CI configuration should be stored in the repository and that Travis and GitLab CI are the future instead of Jenkins and Bamboo. We understand that not everyone will use GitLab CI (most enterprises are using Jenkins) but already have many organizations (including some very large ones) using GitLab CI in production. GitLab CI will undergo massive improvements after integrating it into GitLab itself in 8.0 so you might want to stick with Jenkins if you don't want to be surprised. But we recommend anyone to give GitLab CI as spin while we keep adding features. You'll be happy to know that GitLab 8.1 will ship with a commit status API that makes integrations with third party CI tools easier.

yarper 11y ago
You've gotta look at it this way - when github updates do I even notice? Have you ever had a bug that stopped you working on github? I personally use github all the time and have never seen a bug on it. I trust it completely (well.. tech wise). Our repository is a few million lines, maybe 20,000 commits. The search works fine now it has been changed to call out to git properly (aside from the js searchbox thing in ff). Repositories are stored on the same server. I'm not going to dig up all the issue numbers and turn this into a support request, I am involved in reporting these and commenting on them @ gitlab.com. The syntax highlighting updates have been very well received, but I mean gitlab was shipped with syntax highlighting that doesn't work properly with Java code. Not exactly a unusual lang. And I guess that's where my rant was going - you can't ship crap like that, you should be shipping with 0 known bugs. Every time gitlab ships a bug like this, I take a knock in the office on your behalf and that's why I'm so openly annoyed. Perhaps you could do a LTR or open a beta programme for early adopters?
- sytse 11y ago
  I'm glad to hear most things are working now. We're hiring to put more eyes on the open issues on GitLab.com. If you want a more stable GitLab upgrade to a new minor release on the 21th of every month. At that time all the patches should have landed. We strive to fix all known regressions. If they want to use the bleeding edge people can use our release candidates. Or run master, like we do on our internal server.

by sytse 11y ago

yarper 11y ago

You've gotta look at it this way - when github updates do I even notice? Have you ever had a bug that stopped you working on github? I personally use github all the time and have never seen a bug on it. I trust it completely (well.. tech wise). Our repository is a few million lines, maybe 20,000 commits. The search works fine now it has been changed to call out to git properly (aside from the js searchbox thing in ff). Repositories are stored on the same server. I'm not going to dig up all the issue numbers and turn this into a support request, I am involved in reporting these and commenting on them @ gitlab.com. The syntax highlighting updates have been very well received, but I mean gitlab was shipped with syntax highlighting that doesn't work properly with Java code. Not exactly a unusual lang. And I guess that's where my rant was going - you can't ship crap like that, you should be shipping with 0 known bugs. Every time gitlab ships a bug like this, I take a knock in the office on your behalf and that's why I'm so openly annoyed. Perhaps you could do a LTR or open a beta programme for early adopters?

sytse 11y ago
I'm glad to hear most things are working now. We're hiring to put more eyes on the open issues on GitLab.com. If you want a more stable GitLab upgrade to a new minor release on the 21th of every month. At that time all the patches should have landed. We strive to fix all known regressions. If they want to use the bleeding edge people can use our release candidates. Or run master, like we do on our internal server.