Live data from Hacker News

GitLab 8.15 Released

about.gitlab.com

91–100 of 117 posts

Re: GitLab 8.15 Released

#91
post #45

Are there notable projects or organizations moved to gitlab.com? On top of my head I only know f-droid that is there. I use it for personal use and love it, would love if more projects moved away from github.com, especially open source.

I talked about GitLab and how they can compete against GitHub in this past comment https://news.ycombinator.com/item?id=11155293 and at the present moment, they are still pretty far from being able to convince notable projects to leave github.com for gitlab.com The biggest issue right now, is there is a measurable difference between gitlab.com and github.com, which is, it's much slower. GitLab is working on this and…

If they get to "as good as", they have the advantage of being open source. This could convince _some_ projects.

Re: GitLab 8.15 Released

#92

Earlier quoted context omitted.

Omnibus makes a ton of assumptions about how many things you want bundled, as well as the monolithic configuration is daunting. I'd suggest breaking up into smaller containers for each service. No matter what container medium you choose, the philosophy of omnibus isn't something you want to 'containerize' as it is.

We run gitlab and the full config is 57 lines. A little more than half of those are comments or blank lines. This includes email and oauth. I would suggest not unbundling.

They could do both? Offer the separate parts in an easy-to-use way, and have the bundle re-use those parts.

Re: GitLab 8.15 Released

#93
Thanks for another update! I’ve been running gitlab-ce for over a year now for my sideprojects and random small backups. I don't use any of the more advanced features like ci, but the core has been really great to use.

For reference, i'm running gitlab-ce on a 2 core 2gb vm with 8gb disk and except for one out of memory error about 6 months ago it has been running great for a single user. For more serious use i'd give it way more resources, but for personal use it's humming along perfectly.

Re: GitLab 8.15 Released

#94

I love gitlab! We just deployed our review app deployment to Kubernetes (create a new subdomain in route53, create a new namespace in k8s, create all kubernetes manifests in that namespace, create ingress manifest, boom!). Here's some thing I wish for gitlab: 1. On merge, run "stop_review" so that we don't end up with a lot of old review apps. 2. I wish you could take over https://github.com/sameersbn/docker-gitlab o…

Hi maktouch,

1. Since the review apps is tied with a branch, as soon as branch is deleted the review app is stopped. This actually happening in above video. At the end you see the stopped review :)

2. You can use your own services. Sid did propose to use Helm package. If you look into Helm package sources you will see how they do it and following the same you get the same result on vanilla Docker.

Kamil, GitLab CI Lead

Re: GitLab 8.15 Released

#95

Thanks for another update! I’ve been running gitlab-ce for over a year now for my sideprojects and random small backups. I don't use any of the more advanced features like ci, but the core has been really great to use. For reference, i'm running gitlab-ce on a 2 core 2gb vm with 8gb disk and except for one out of memory error about 6 months ago it has been running great for a single user. For more serious use i'd giv…

Thanks for posting, glad you're happy with the update.

2GB for a single user should be enough. To prevent the out of memory error since using the Omnibus package and configuring 1 or 2GB of swap space if you haven't done so already.

Re: GitLab 8.15 Released

#96
post #88
post #87

Gitlab has too many downtimes for upgrading. When I got a failed push I was saying: Oh gitlab has a new version... :meh:

The downtime for upgrading is annoying. We're trying to get to a point where the database migrations don't require downtime. But the deploy of 8.15 caused 40 minutes of downtime, this is not acceptable. For the post-mortem please see https://dev.gitlab.org/gitlab/organization/issues/1082

Oops, that is not a public link. I've made adjustments to our handbook to move it to GitLab.com so it can be public https://gitlab.com/gitlab-com/www-gitlab-com/commit/7fc274a1...

Re: GitLab 8.15 Released

#97
post #91
post #45

Earlier quoted context omitted.

I talked about GitLab and how they can compete against GitHub in this past comment https://news.ycombinator.com/item?id=11155293 and at the present moment, they are still pretty far from being able to convince notable projects to leave github.com for gitlab.com The biggest issue right now, is there is a measurable difference between gitlab.com and github.com, which is, it's much slower. GitLab is working on this and…

If they get to "as good as", they have the advantage of being open source. This could convince _some_ projects.

Note that gitlab.com runs on GitLab EE, their commercial product, which is not FOSS. This is why the GNU project hosts their own instance of GitLab CE for themselves.

Re: GitLab 8.15 Released

#98

I recently registered to try gitlab. I received unprecedented large amounts of spam from them daily with no unsubscribe button. I finally emailed them to stop the spam and they did but not completely I received more but had unsubscribe this time. Unsubscribed so lets see what happens. One more spam and I will close my account and never try them again GitHub is great, does the job incredibly well, doesn't get in the w…

Hi, thank you for bringing this to our attention. If you wouldn't mind getting in touch with Mitchell (commented below) or myself at jennifer [at] gitlab [.] com, we can look at your particular situation.

To share a little background, our marketing automation system does have a limit to the number of emails a person can receive: max of 2 per day; 5 per seven days; and no limit to operational emails. Operational emails are things like a signup confirmation, EE trial license key & initial download instruction.

There are a certain periods of time that have the potential to create a "perfect storm" of emails to be sent/received in short succession.

Example of "perfect storm": If a person signs up for GitLab and download an EE trial the day or two before the bi-weekly newsletter email is sent, they could receive 3 operational emails and 1 marketing email in the first 24 hours.

Please let me know if you have additional questions or if I can explain something more clearly.

Re: GitLab 8.15 Released

#99
post #98

I recently registered to try gitlab. I received unprecedented large amounts of spam from them daily with no unsubscribe button. I finally emailed them to stop the spam and they did but not completely I received more but had unsubscribe this time. Unsubscribed so lets see what happens. One more spam and I will close my account and never try them again GitHub is great, does the job incredibly well, doesn't get in the w…

Hi, thank you for bringing this to our attention. If you wouldn't mind getting in touch with Mitchell (commented below) or myself at jennifer [at] gitlab [.] com, we can look at your particular situation. To share a little background, our marketing automation system does have a limit to the number of emails a person can receive: max of 2 per day; 5 per seven days; and no limit to operational emails. Operational email…

What can Gitlab possibly mail me 5 times per week?

I don't understand why this is not max 5 times per month.

Re: GitLab 8.15 Released

#100

Earlier quoted context omitted.

We've spent quite a bit of time this year improving performance, GitLab.com is still slower than it should be but it's a lot better now than it was in January. Self-hosted instances that meet the recommended specs are already fairly performant, though we're always working to improve things regardless. As mentioned in the blog post, this release we decreased page size a lot (from 1800kb to 718kb for a given Merge Requ…

This probably sounds like a strange comment/question, but one of the reasons I haven't moved over to gitlab is that I know that it is unlikely that I will every be a paying customer. I actually don't mind that much about the performance issues (because I really just want cloudy git storage), but I don't like to take something for free unless I know the person giving it really wants to give it... So as strange as it s…

Networking effects are serious stuff. If you use it, you’re more likely to recommend it to others—or for public stuff, others will see you using it—and then they’ll start using it. And some of them will pay.
Post reply on HN