GitLab Database Incident – Live Report

Re:GitLab Database Incident – Live Report by eblanshey on Wednesday February 01, 2017 @12:52AM (#13538616)

Would you mind explaining what you like about gitlab better than bitbucket? They seem to be on par with each other, including integrated CI.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by songzme on Wednesday February 01, 2017 @07:17AM (#13540111)

I like gitlab's issue tracking. Its faster (from a productivity standpoint) and easier to manage compared to Jira + Bucket, which feels a bit too bloated.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by 0x0 on Wednesday February 01, 2017 @01:52AM (#13538886)

For me, privately self-hosted CI runners was a killer feature. Bitbucket only seemed to offer limited-minutes shared runners when I looked.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by yjlim5 on Wednesday February 01, 2017 @06:46AM (#13539942)

One major reason was that our team was growing and Gitlab allowed us to add them, whereas BitBucket was limited to 5 devs.

[ Parent | on HN ]