What we learned after a year of GitLab.com on Kubernetes
What we learned after a year of GitLab.com on Kubernetes It's been one year since we moved GitLab.com to Kubernetes. We unpack the challenges and learnings from this major migration. For about a year now, the infrastructure department has been working on migrating all services that run on GitLab.com to Kubernetes. The effort has not been without challenges, not only with moving services to Kuberne
GitLab’s journey from Azure to GCP
GitLab’s journey from Azure to GCP GitLab Staff Engineer Andrew Newdigate shares how we completed our migration to Google Cloud Platform, and how we overcame challenges along the way. Last June, we had to face the facts: Our SaaS infrastructure for GitLab.com was not ready for mission-critical workloads, error rates were just too high, and availability was too low. To address these challenges, we
How we do Vue: one year later
How we do Vue: one year later How we, at GitLab, write VueJS, one year later. It's been a while since we wrote about Vue. We've been using Vue for over a year now and life has been very good. Thanks @lnoogn for reminding me to write this article! Our situation reminds me of a quote about Scala from "Is Scala slowly dying?" Someone once said: Scala people don't have time for redditing and blogging,
We're switching to a DCO for source code contributions
We're switching to a DCO for source code contributions We want to make it even easier for everyone to contribute, by doing away with our Contributor License Agreement in favor of the Developer's Certificate of Origin. We're committed to being good stewards of open source, and part of that commitment means we never stop re-evaluating how we do that. Saying "everyone can contribute" is about removin
Postmortem of database outage of January 31
Postmortem of database outage of January 31 Postmortem on the database outage of January 31 2017 with the lessons we learned. On January 31st 2017, we experienced a major service outage for one of our products, the online service GitLab.com. The outage was caused by an accidental removal of data from our primary database server. This incident caused the GitLab.com service to be unavailable for man
What is GitLab Flow?
GitLab Flow prevents the overhead of releasing, tagging, and merging to streamline development. Git simplifies branching and merging, leading software development teams to move away from other source control tools, like SVN, and adopt a workflow to simplify development. Organizations moving to Git from other version control systems may have difficulty identifying an effective workflow. GitLab Flow
GitLab Annex solves the problem of versioning large binaries with git
GitLab Annex solves the problem of versioning large binaries with git GitLab solves the biggest limitation of git compared to some older centralized version control systems has been the maximum size of the repositories. WARNING git-annex support on GitLab EE was deprecated in GitLab 8.17 (2017/02/22), and was permanently removed in GitLab 9.0 (2017/03/22). Read through the migration guide from git
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Remote only