April 2016 Summaries

GitLab.com operates on a robust infrastructure designed to efficiently handle its application processes and user demands, consisting of 45 directly managed servers including HAProxy load balancers, workers running the GitLab EE application stack, NFS, Redis, PostgreSQL, and Elasticsearch servers. Additionally, the platform utilizes Azure's Availability Sets for redundancy and high availability in load balancing, Redis, PostgreSQL, and Elasticsearch, along with a Shared Runners manager for autoscaling, which slightly increases the server count. Beyond these core elements, GitLab.com dynamically scales with Docker-based build hosts for Shared Runners, fluctuating between 60 and 200 servers based on demand, reflecting the scalable and responsive nature of its infrastructure. The detailed breakdown highlights the complexity and adaptability of GitLab.com's server management necessary to maintain its large-scale operations.

The tutorial provides a comprehensive guide on setting up and managing a GitLab server using DigitalOcean's One-Click Install Image to handle Git repositories efficiently. It highlights the importance of version control in software development and introduces GitLab as a Git repository management server that can be easily deployed on a DigitalOcean droplet. The tutorial walks through the process of creating a GitLab droplet, configuring domain names and emails, logging into the GitLab server, and modifying account information to reflect personal details. It also covers the steps for updating to newer releases, ensuring the server remains current with the latest features and security updates. The tutorial emphasizes the ease of managing user access, configuring repositories, and monitoring projects' issues and commits while encouraging users to explore GitLab's help system and official documentation for additional configuration options.

Working at GitLab is characterized by several recurring themes highlighted by team members, including the quality of people, the product, open-source values, freedom, and opportunity. Employees appreciate the talented and approachable nature of their coworkers and enjoy working on a product they are passionate about, with open-source involvement providing additional motivation. GitLab's remote-only structure offers employees significant independence, attracting individuals who value personal freedom. The company fosters an environment ripe with opportunities for learning and growth, encouraging team members to take on varied roles and responsibilities while contributing to a community focused on continuous improvement. Regular feedback through anonymous surveys ensures that employees' thoughts and concerns are acknowledged and addressed, contributing to a high level of job satisfaction.

The 8.6 release introduced a feature allowing users to move issues between projects, addressing the common problem of mistakenly creating issues in the wrong project. This feature ensures that when an issue is moved, the original is copied, closed, and referenced, maintaining all progress and notifying subscribers based on their settings. Although seemingly simple, implementing this feature posed challenges, particularly with ensuring cross-project references in descriptions and comments remain accurate. Developers initially faced difficulties with Markdown references and labels, leading to a solution involving regular expressions to match local references and substituting them with fully-expanded cross-project references. This approach, while not the most performance-efficient, enabled a timely release, ensuring the integrity of issues and comments.

GitLab provides built-in continuous integration capabilities, utilizing Runners to process various build tasks like creating software packages or running tests, as defined in a YAML file. Introduced in March, GitLab Runner 1.1 offers autoscaling features, beneficial for users of GitLab.com’s shared Runners. This tutorial guides users on setting up a specific Runner on DigitalOcean, emphasizing the use of the Docker executor due to its compatibility. It details the process of creating a Docker droplet on DigitalOcean, installing the GitLab Runner on it, and registering the Runner with a specific GitLab project using a unique token. The tutorial highlights the flexibility of using various operating systems and the ability to register multiple Runners on a single droplet, facilitating targeted project builds.

GitLab has partnered with DigitalOcean to address scaling challenges in Continuous Integration (CI) by providing free Runners for GitLab.com projects and offering discount codes for GitLab Community and Enterprise Edition users. This collaboration aims to enhance speed, security, and cost-effectiveness in testing and deployment processes by leveraging DigitalOcean's ability to rapidly provision new servers, significantly reducing the time needed to start instances compared to other cloud providers. The partnership introduces a new autoscaling feature for GitLab Runner, enabling dynamic instance management to support efficient parallel testing. This integration aligns with both companies' commitment to simplifying and scaling cloud infrastructure, offering developers a streamlined, secure, and affordable solution for coding, testing, and deploying applications.

In projects with numerous issues, such as GitLab, keeping track of topics of interest can be challenging, especially with the influx of contributors. To address this, GitLab introduced a feature in version 8.6 that allows users to subscribe to specific labels, ensuring they receive notifications for issues tagged with those labels, regardless of their general notification settings. This is particularly useful for individuals like GitLab's performance expert, Yorick, who subscribes to the performance label to stay informed about relevant issues without being overwhelmed by the volume of unrelated ones. New team member Amara Nwaigwe also utilizes this feature to maintain visibility on topics pertinent to her interests. Users are encouraged to explore upcoming features and provide feedback by visiting GitLab's Direction page to gain insights into their roadmap.

GitLab's gitlab-workhorse, initially a small weekend project developed in Go to address git clone timeouts, has evolved into a critical component that processes almost all HTTP requests for GitLab. Originally, GitLab relied on the Unicorn Ruby web server, which was incompatible with long-duration requests like git clone due to its short request timeout settings. This led to the development of gitlab-git-http-server in Go, which circumvented these timeout issues and was later integrated into GitLab, eventually becoming gitlab-workhorse. Over time, gitlab-workhorse expanded its capabilities beyond handling Git HTTP clients to include features such as handling the 'download zip' button, Git LFS support, and CI build artifacts, prompting a name change. This development, driven by both technical necessity and personal curiosity about Go, allowed GitLab to simplify its NGINX configuration by routing all HTTP requests through gitlab-workhorse, thus facilitating easier deployment across different web servers. The project's success highlighted the need for more team involvement to alleviate dependency on its creator and address technical debt, with plans to enhance request handling to improve performance further.

The text provides a comprehensive guide on adding HTTPS to a GitLab Pages site using Let's Encrypt, emphasizing the importance of TLS/SSL for security, including authentication, data integrity, and encryption. It highlights the push for universal TLS adoption, noting Google's use of HTTPS compliance for website ranking since 2014. The guide details the process of obtaining a free TLS certificate from Let's Encrypt, configuring a static blog with Jekyll, and uploading the project to GitLab. It explains how to handle custom domain TLS certificates by manually setting up Let's Encrypt and creating necessary challenge files to verify domain ownership. The text also covers redirecting traffic to HTTPS and ensuring compatibility with search engines and internal links. Additionally, it discusses potential issues with JavaScript-based redirects and encourages contributing to GitLab's support for Let's Encrypt.

GitLab's shift to a "remote only" company has been embraced by many of its team members, especially those who are parents, as it offers significant benefits such as increased family time and flexibility, eliminating lengthy commutes and allowing for a better work-life balance. Employees appreciate the ability to participate more actively in family life, as seen in examples like sharing meals and flexible parenting hours. While remote work boosts productivity, challenges arise from blurred boundaries between work and personal life, which can lead to distractions and increased expectations for household responsibilities. Parents at GitLab manage these challenges by establishing clear boundaries, using asynchronous communication, and sometimes working outside the home to maintain focus. The company supports its remote staff by providing resources like ergonomic equipment and covering costs for Internet and office space, fostering a supportive and productive work environment that integrates home life into the professional sphere.

Stack Overflow, a global support network for programmers, has adopted GitLab as its primary source control solution, following initial trials with Git-web and Kiln, due to GitLab's superior development and performance enhancements. Operating largely remotely from its New York headquarters, Stack Overflow's development team of 30 leverages GitLab on-premises, while opting for Team City instead of GitLab's integrated CI, and employs a self-hosted chat system. The use of GitLab has been pivotal in the company's ongoing efforts to provide a reliable and maintainable platform for building a comprehensive library of programming solutions. Stack Overflow developers, who are active in the open-source community, have experienced improvements in development time, code review, and collaboration, and have started using LDAP integration and exploring GitLab Geo for potential solutions to multi-datacenter replication challenges. The team emphasizes maintenance, reliability, and maintainability as crucial considerations, and they are eager to enhance their search experience to further benefit their work.

The article provides a comprehensive guide on using GitLab Pages to host static websites for free on GitLab.com, detailing the process from creating a new project to configuring GitLab CI with a .gitlab-ci.yml file. It emphasizes the compatibility of GitLab Pages with various Static Site Generators (SSGs) like Jekyll, Hugo, Hexo, and Middleman, and explains how to manage multiple websites for different users or groups. The tutorial also covers the advantages of using GitLab CI to control builds, validate configurations, and utilize custom domains with SSL/TLS certificates for enhanced security. Readers are guided through setting up GitLab Pages projects, including creating a new project, uploading website content, and optionally adding a custom domain, with practical examples and tips for effective website management on GitLab.

GitLab, a supporter of open-source projects, participated in the Git Merge event sponsored by several tech companies to discuss the development and direction of Git, a core component of their service. The event highlighted the growing adoption of Git by larger organizations, which has led to efforts to improve its performance, such as through repacking, to handle large repositories efficiently. The protection of the Git trademark by the Software Freedom Conservancy was emphasized as crucial to safeguarding the software and its users from misuse. The event also underscored the need for increased diversity within the tech community, prompting GitLab to enhance its diversity sponsorship programs. Initiatives like Gnome's Outreachy and Google Summer of Code were noted for their support of diversity in tech. Additionally, the summit addressed potential improvements in Git's submodule functionality and the Submit Git tool, which bridges GitHub and the Git mailing list, allowing for a streamlined patch submission process. GitLab expressed gratitude for being part of these discussions and looks forward to future collaborations.

The blog post discusses the recent updates to GitLab's SaaS Runners, focusing on the introduction of autoscaling to better accommodate continuous integration (CI) demands on GitLab.com. This enhancement aims to reduce build times by automatically adjusting the number of virtual machines (VMs) available to handle tasks, which run in Docker containers on Digital Ocean 4GB instances. GitLab offers free Shared Runners for projects, both private and public, allowing users to connect their own runners without additional charges. The update also involves changes to the default configuration, removing unnecessary services like MySQL and PostgreSQL unless specified by users, to streamline operations and enhance security, as each build is executed on fresh VMs. The post encourages users to adjust their .gitlab-ci.yml files accordingly, while highlighting a scheduled webcast for further insights into using GitLab CI, providing an opportunity for users to engage with the GitLab CI team and address any queries about the platform.

GitLab Pages offers a free service for hosting static websites, which was introduced in GitLab Enterprise Edition (EE) 8.3 and later enhanced with custom domain and TLS certificate support in version 8.5. Available on GitLab.com, this service accommodates unlimited public or private projects and supports various static site generators like Jekyll, Pelican, and Hugo. Users can utilize the provided resources, such as a quickstart guide and improved documentation, to set up and manage their sites effectively. GitLab Pages is integrated with GitLab CI, enabling automated deployment workflows, and the platform offers a webcast for users to learn more about the service and engage with the GitLab CI team.