June 2019 Summaries

During a two-week rotation in GitLab's CEO shadow program, the author observed the repetitiveness inherent in the role of CEO Sid Sijbrandij, who frequently reiterated key themes such as GitLab's all-remote culture, company values, and the importance of an actionable agenda. The all-remote model, a popular topic among investors and potential hires, is underpinned by tools like GitLab's handbook and Google Docs, which facilitate collaboration and communication across a global team. Transparency and a data-driven approach are emphasized, with Sid encouraging iteration and efficiency in processes. The program highlighted the significance of clear communication and the use of technology to foster inclusivity and productivity. Sid's appreciation for his team, demonstrated through frequent expressions of gratitude, stands out as an essential leadership quality.

CI/CD (Continuous Integration and Continuous Delivery) strategies significantly enhance software deployment by allowing DevOps teams to innovate rapidly, improve code quality, and attract talent while reducing errors and manual tasks. Companies that adopt robust CI/CD frameworks, including tools like containers and Kubernetes, can quickly deliver functional applications, thus gaining a competitive edge in the market. The effectiveness of CI/CD strategies can be measured through metrics such as cycle time, time to value, uptime, error rates, infrastructure costs, and team retention rates. A well-implemented CI/CD approach not only optimizes operations and development processes but also fosters a positive engineering culture that supports the entire DevOps lifecycle, ultimately benefiting the whole organization.

In its 12.1 release, GitLab concluded its deprecation of MySQL support, a decision driven by several limitations and inefficiencies associated with maintaining dual database backends of MySQL and PostgreSQL. MySQL's inability to handle nested groups, requirement for hacks to increase column limits, lack of support for partial indexes, and inability to add TEXT type columns without specified lengths were among the challenges that hindered GitLab's performance and development velocity. Supporting both databases led to complex code and increased costs, as testing suites had to be run twice, slowing down GitLab's continuous integration system. Despite some use cases for MySQL, the majority of GitLab's user base had already transitioned to PostgreSQL, as evidenced by Usage Ping data showing that over 110,000 instances were using PostgreSQL compared to less than 1,200 with MySQL. This shift allowed GitLab to optimize their platform using PostgreSQL-specific features like LATERAL JOIN, ultimately enhancing GitLab's efficiency and reliability. GitLab users still on MySQL are encouraged to migrate to PostgreSQL, with resources available to assist in the transition.

Alexander Dietrich, a Senior Security Engineer at GitLab, shares insights into his role and the nature of working in one of the most transparent organizations. Since joining GitLab in September 2018, he has been instrumental in creating tools to automate security tasks, enhancing both speed and consistency within the team. The dynamic environment at GitLab presents ongoing challenges and rewards, as there is always new technology to learn and implement. Dietrich emphasizes the importance of efficiency and highlights key initiatives like meeting security remediation goals and advancing GitLab’s Zero Trust initiative. He discusses the evolution of his field from traditional software development to cloud-native security practices and stresses the importance of using password managers and keeping systems updated. Looking ahead, he hopes for a future where security and usability are not at odds and advocates for more research into decentralized, secure systems. Beyond his professional insights, he shares personal preferences such as favoring Vim over Emacs, Ubuntu as his preferred Linux distribution, and Darjeeling tea as his beverage of choice.

GitLab's commitment to an all-remote work philosophy is exemplified through the experiences of Sarah Daily, a digital marketing programs manager, who embraces the flexibility of remote work while living as a digital nomad in a 40-foot travel trailer. After transitioning from a traditional office job in a non-profit organization, Sarah sought out a position at GitLab due to her passion for technology and remote work, finding that the company's culture and values deeply resonated with her. GitLab's asynchronous work model, which allows employees to work across various time zones without the constraints of a central headquarters, has enabled her to travel extensively across the US and Canada, enjoying the freedom to design her workday around personal productivity and life commitments. The transparency and inclusivity at GitLab create an environment where employees feel valued and part of a shared goal, distinguishing it from other companies and fostering a strong sense of community and innovation.

The GitLab Q2 Hackathon took place on May 29-30, bringing together a vibrant community of contributors who submitted 44 merge requests (MRs), with over 30 being merged within two weeks, despite the event coinciding with a holiday week in many countries. The event encouraged just-in-time problem-solving, as highlighted by an issue being quickly picked up during a GitLab Monitor tutorial session. Participants whose MRs were merged received tokens of appreciation, with Marcel Amirault winning the grand prize for having the highest number of merged MRs, while Michel Engelen and Marc Schwede tied for second place. Feedback from the event suggested announcing future Hackathon dates earlier, leading to the announcement of the Q3 Hackathon for August 28-29, with further details to be shared as the date approaches. Those interested in contributing are encouraged to visit the Contributing to GitLab page for guidance on how to get involved in various aspects of the project, and can reach out to the community for support.

Continuous integration and delivery (CI/CD) are crucial for DevOps teams aiming to enhance software quality and speed, yet not all CI/CD implementations are equally effective. This discussion highlights the significant business impacts of inadequate CI/CD strategies, such as increased IT spending on maintenance, delayed or unrealized revenue due to inefficient processes, and decreased developer productivity and satisfaction. Poor CI/CD can lead to opportunity costs as engineering resources are diverted from innovation to maintenance, and delays in code deployment can result in lost revenue. A robust CI/CD system, however, allows more engineers to focus on creating business value, facilitates rapid and automated code deployment, and enables developers to concentrate on solving business problems with the support of operations teams. Modernizing architecture to embrace CI/CD practices not only improves software release quality and speed but also contributes to long-term revenue growth. The text suggests exploring GitLab CI/CD for effective implementation, as it has been highly rated by Forrester.

In a conversation between leadership psychologist Banu Hantal and GitLab CEO Sid Sijbrandij, the discussion focuses on Sid's partnership with co-founder Dmitriy Zaporozhets and the origin of GitLab. Sid highlights the importance of transparent communication in maintaining their partnership, which began online when Dmitriy launched GitLab and Sid saw its potential as a service. Sid independently started GitLab.com, later reaching out to Dmitriy, whose interest in working full-time on GitLab catalyzed its growth. Despite having a mostly remote relationship, Sid emphasizes that regular communication is key to their successful collaboration, allowing them to address issues proactively. The company structure at GitLab facilitates engineers' advancement without moving into management roles, allowing Dmitriy to remain an engineering fellow. Their collaborative efforts led to significant technical advancements, including the creation of GitLab's CI solution. Sid reflects on their partnership as one based on mutual respect for each other's work, suggesting that such business-based friendships are often more enduring.

Scoped Labels, a feature available to certain GitLab subscription tiers, are designed to enhance custom workflows by allowing teams to apply mutually exclusive labels to issues, merge requests, or epics. This feature helps eliminate confusion and streamline issue lists by automatically removing existing related labels when a new one is applied, similar to moving issues across label lists in an issue board. By defining workflow steps such as proposal, design, development, and deployment, Scoped Labels reduce cycle times and enable teams to work concurrently on features while measuring their progress based on how long issues retain specific labels. This functionality, although seemingly minor, aids in maintaining organized and efficient workflows and is readily accessible for demonstration in the provided documentation.

As DevOps adoption matures, organizations are increasingly integrating security into their development processes, leading to the evolution of DevSecOps, which combines development, operations, and security into a unified framework. GitLab 12.0 enhances this integration by offering a single application that incorporates security features such as Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), dependency scanning, and container scanning directly into the continuous integration/continuous deployment (CI/CD) pipeline. This version also introduces new capabilities like Auto Remediation, Security Dashboards, and Security Approvals, enabling developers to identify and address vulnerabilities early in the development cycle. By automating security processes and providing a cohesive platform for collaboration, GitLab aims to streamline the development workflow, reduce potential bottlenecks caused by security reviews, and improve overall productivity, as highlighted by users who have benefited from the integrated approach. The single application model reduces context switching and enhances toolchain management, ultimately supporting faster and more secure software delivery.

GitLab's 11.x series introduced a range of features aimed at enhancing cloud-native CI/CD processes with integrated security and automation. Starting with the 11.0 release in June 2018, GitLab launched Auto DevOps, which automates the entire delivery process to Kubernetes clusters, making it easier for teams to deploy applications. Subsequent releases, such as 11.1 and 11.2, focused on security enhancements and custom templates, respectively, while integrating tools like Kaniko for secure Docker builds. The series also saw the introduction of interactive web terminals, improved CI/CD pipeline visibility, and the inclusion of languages like JUnit for testing. By the 11.5 release, GitLab had added access control for Pages and enabled Knative deployment for serverless applications. The 11.7 release further expanded on package management with the introduction of an NPM package repository. Throughout these updates, GitLab consistently emphasized the importance of feedback-driven development and collaboration with its user community, ensuring that the platform evolves to meet the needs of modern DevOps practices.

Daniel Juarez, an associate at CERN's Version Control Systems team, has been enhancing and supporting the GitLab setup and continuous integration infrastructure at CERN since joining in 2017. Hailing from the University of Oviedo, he contributes to GitLab as part of his role, tackling issues like storage performance and participating in the community through merge requests and issue tracking via CERN's internal Jira system. Juarez emphasizes the collaborative nature of working with GitLab, praising the responsiveness of its team in addressing community concerns, although he notes a worry about the volume of unresolved issues. He highlights the significance of contributions like SAML support and Shared CI Runners, which have notably improved services for CERN's extensive user base. Beyond work, Juarez enjoys gaming, watching bad movies, and cooking, encouraging others to contribute to GitLab by leveraging resources like the Contributing to GitLab page.

GitLab operates as an all-remote company with a workforce distributed globally, allowing team members to work asynchronously across different time zones, which creates a competitive edge by ensuring continuous contributions throughout the day. This flexible work environment emphasizes results over a traditional work schedule, enabling employees to structure their workdays according to personal preferences, whether they are early risers or night owls. The company culture supports a balance between personal and professional obligations, particularly benefiting working parents who can integrate family responsibilities into their day. Team members engage in various routines depending on their location, lifestyle, and commitments, with some choosing to focus on deep work during quiet hours and others collaborating with colleagues when their time zones overlap. GitLab's commitment to its core values of collaboration, results, and transparency fosters an environment where employees can thrive, leading to its recognition as one of the best places to work by Inc. Magazine.

Microservices architecture has become influential for organizations aiming to enhance automation and deployment speed, with major companies like Amazon, Netflix, and Google adopting this model. Unlike monolithic architectures, where all components are part of a single unit, microservices break down applications into individually deployable services that communicate via APIs. This approach offers greater flexibility, reliability, and innovation speed for complex applications, although monoliths are not without their advantages, such as simplicity. Transitioning to microservices can be achieved through various methods, such as the gradual strangler method, the hybrid Lego strategy, or the risky nuclear option of starting from scratch. Verizon's successful transition to microservices, which reduced deployment times significantly, highlights the importance of clear objectives and the prioritization of specific outcomes. With advancements in container orchestration, CI/CD tools, and automated APIs, developing with microservices has become more accessible, enabling developers to focus on innovation instead of manual tasks. Despite being more complex than monoliths, the benefits of microservices, such as streamlined processes and automated simplicity, make them a compelling choice for modernization efforts.

Roger Ostrander, a Senior Security Engineer at GitLab, plays a crucial role in combating spam, Bitcoin mining, phishing, and malware by creating automated tools for early detection and prevention. Having started in backend web programming and machine learning, his journey into security was unexpected, sparked by an interview at Reddit focused on fighting spam. His diverse experience, including technical sales as a solutions architect, has provided him with a broad perspective on systems at scale. Ostrander faces the unique challenge of balancing transparency with security at GitLab, ensuring that anti-abuse measures are effective without revealing tactics to potential offenders. He reflects on past professional failures, such as accidentally banning Reddit's front page, and the importance of thoroughness and logging in security operations. Despite the serious nature of his work, Ostrander maintains a lighthearted approach, engaging in debates over topics like "Is a hotdog a sandwich?" while emphasizing the importance of continuous learning and adaptation in his field.

Adopting an Agile mindset is crucial for IT leaders aiming to effectively reduce cycle time and foster innovation within software development teams. Instead of merely accumulating tools, IT leaders should focus on cultivating an Agile mindset that emphasizes viewing setbacks as learning opportunities, embracing iteration, collaboration, and change, and prioritizing the delivery of value over mere output. This mindset encourages teams to experiment without fear, facilitating creativity and problem-solving, while enhancing cross-collaboration and adaptability to market changes. The shift to an Agile mindset can be challenging as it involves altering long-standing beliefs and approaches to problem-solving, but can be achieved by modeling desired behaviors, sharing success stories from other organizations, and implementing gradual changes. Ultimately, an Agile mindset enables teams to swiftly adjust to dynamic market demands, integrate customer feedback efficiently, and deliver tangible business value, thereby transforming team culture by eliminating fear, enhancing collaboration, and removing delivery obstacles.

Markdown, initially created by John Gruber, has become a popular method for writing online content due to its simplicity and ability to be converted into HTML or XHTML. Over time, various "flavors" of Markdown emerged, causing inconsistencies in rendering across different platforms. In response, GitLab adopted CommonMark, a standardized specification designed to ensure consistent Markdown rendering, as part of a phased migration. Initially, CommonMark was implemented for new content only, later extending to repository and wiki files, and ultimately replacing the previous RedCarpet rendering system entirely. This transition aimed to reduce technical debt and improve user experience by providing more consistent rendering, though it required some upstream improvements, such as supporting double-tilde strikethroughs. GitLab's adoption of CommonMark aligns with other platforms like GitHub and Discourse, enhancing the overall usability and compatibility of Markdown content across various applications.

In modern app development, using containers has become a standard practice due to their value in building applications, but developers are increasingly turning to serverless architecture to eliminate the need to manage infrastructure and instead focus on the app's business logic and user interaction. This shift towards serverless aligns with the trend of moving away from monolithic applications to microservices architecture, offering increased velocity, flexibility, and scalability. A webinar titled "Running containerized applications on modern serverless platforms," scheduled for June 25, 2019, with experts from GitLab and Google, promises to explore how technologies such as Kubernetes, Knative, Cloud Run, and GitLab Serverless can enhance application stability and scalability while reducing costs and fostering innovation.

Security compliance frameworks are struggling to keep pace with the rapidly evolving technology landscape, which has shifted significantly from traditional network models to cloud-based and serverless computing environments. This evolution is characterized by advancements such as infrastructure deployment via code, containerization, and the growing adoption of zero trust principles, which depart from the conventional network perimeter model. The transition to remote work, as exemplified by GitLab's all-remote setup, further complicates compliance, as old frameworks often fail to accommodate modern security practices. Compliance frameworks like FedRAMP are beginning to adapt by standardizing approaches for cloud environments, yet there is a pressing need for them to become more relevant and supportive of actual security measures. GitLab is contributing to this evolution by developing and open-sourcing its own compliance framework, aiming to provide a real-world reference for other organizations. The ongoing dialogue within the technology community emphasizes the importance of aligning compliance standards with current security needs to better protect consumers, encouraging collective input and collaboration to drive meaningful progress.

The GitLab Manage team discussed maintaining agility in a scaling organization, emphasizing the importance of quick decision-making, hiring the right people, and keeping teams small and focused. They highlighted the necessity of distinguishing between Type-1 and Type-2 decisions, with the latter being easily reversible and requiring lower approval thresholds. Agile practices are viewed as essential for delivering incremental value and adapting to feedback. The conversation also stressed the value of allowing teams to experiment with processes, while maintaining some standardization in shared codebases. Ensuring alignment on what it means to be agile, both in understanding and in practice, is deemed crucial for effective change within the organization. The team recognized the potential pitfalls of large teams, which can lead to inefficiencies and stressed the importance of leadership's role in supporting agile methodologies.

Proximus, a leading Belgian telecommunication company, has successfully integrated GitLab into its CI/CD DevOps workflow to enhance its application development and deployment processes. Initially using ClearCase, Proximus switched to GitLab in 2016 due to its user-friendliness and broader compatibility, starting with GitLab CE and later upgrading to GitLab EE to access additional features like LDAP groups and push rules. This transition facilitated a significant increase in project numbers and user adoption, with projects growing to 1,700 and users to nearly 1,000 by the end of 2018. Despite challenges such as maintaining a stable environment amid rapid growth and resource consumption issues due to numerous pipelines, Proximus effectively managed these with GitLab's features, resulting in a substantial reduction in support tickets by 80 percent in the first year. The company plans to continue expanding its GitLab environment, leveraging its benefits for enhanced developer support and efficiency.

GitLab.com celebrated a significant milestone in March 2019, reaching a record 1 million merge requests (MRs), with another million following in April, marking a 17% increase in engagement from February to March. This surge was primarily driven by private project MRs, although there is potential for increased community participation in public projects. GitLab's design enables contributors from diverse backgrounds, including developers, project managers, and writers, to collaborate on projects, transforming ideas into actionable changes. Contributions vary from technical enhancements to operational improvements, such as refining the onboarding process or documentation, and the platform welcomes first-time contributors, emphasizing that contributions are not limited to code. Senior product manager Jeremy Watson highlights the importance of community support in achieving GitLab's vision of facilitating innovation through a single application, while Ray Paik notes that recent releases have seen 40-50 new contributors, many of whom began by improving documentation.

Continuous integration and delivery (CI/CD) aims to enhance software quality and expedite delivery for DevOps teams, but challenges remain in its implementation, particularly in modernizing CI/CD processes to overcome barriers such as high maintenance costs and development slowdowns. Key issues include the allocation of significant resources to maintain complex toolchains rather than delivering business value, and conflicts between development and operations teams due to differing incentives for innovation versus stability. Additionally, developers often face difficulties with environment dependencies and context switching, which can delay production and demoralize them as they manage both development and operations tasks. This article encourages considering tools like GitLab CI/CD to address these challenges by offering a more integrated and efficient approach to CI/CD.

GitLab's Contribute 2019 event in New Orleans was a celebration of community and collaboration, emphasizing the company's commitment to remote work and its inclusive culture. During the gathering, CEO Sid Sijbrandij highlighted the importance of contributions from the community, which reached a record high just before the event, and encouraged attendees to embrace the ethos that everyone can contribute. The event featured a mix of networking, team-building activities, and inspiring keynotes, leaving attendees like Heather Simpson and Philip Camillo feeling motivated and connected to their colleagues. The focus on relationship-building and collective improvement resonated with participants as they shared personal reflections and insights, demonstrating the profound impact of collaboration on GitLab's success and growth.

GitLab's transition from traditional synchronous department meetings to a more efficient, asynchronous podcast-style format aimed to address the challenges of remote work and large meeting sizes. The change was proposed to enhance efficiency and reduce the "soul-sucking" nature of lengthy synchronous meetings, while still maintaining the informational and connective aspects of such gatherings. Despite concerns that face-to-face meetings foster personal connections, GitLab encourages employees to engage in informal "coffee chats" and scheduled small group video calls to build relationships. The new format, which includes automated Slack reminders for contributions and discussions, allows employees to consume content passively and multitask, aligning with GitLab's remote work culture. This shift compresses the meeting time significantly, while still ensuring that key information is communicated effectively and efficiently, demonstrating a successful adaptation to remote work challenges.