February 2019 Summaries

GitLab's compensation strategy, which frequently attracts attention in discussions about the company, involves paying employees based on local market rates rather than a standardized global salary. This approach emerged organically as the company grew, initially considering previous salaries but later focusing on aligning pay with local market conditions, reflecting both job function and geographic location. GitLab's compensation model incorporates a rent index derived from Numbeo to gauge local rates, ensuring fairness by analyzing multiple data sources to establish a median benchmark. This method allows GitLab to hire and retain talent effectively across diverse geographic regions without inflating costs or concentrating employees in low-wage areas. While some criticize location-based pay as inequitable, GitLab argues that standardizing salaries could limit hiring and production capabilities, particularly in high-cost cities. The company advocates for remote work and hopes that as more companies adopt this model, compensation disparities will diminish, fostering a more equitable global pay structure.

The author, a Product Manager at GitLab, reflects on their evolving perspective of remote work, initially seen as a challenge but now viewed as a competitive advantage for the company. The key to GitLab's successful remote model lies in its commitment to asynchronous communication, transparency, and an inclusive culture where everyone can contribute. By emphasizing written communication, GitLab ensures geographic and time zone diversity, promoting clarity and reducing the need for synchronous meetings. Transparency fosters honesty and collaboration, enabling a single source of truth accessible to all. The company's iterative approach encourages rapid feedback and action, allowing for quick adaptation and innovation. While the volume of communication can be overwhelming for new employees, the company relies on the wisdom of crowds and well-defined roles to manage this dynamic environment effectively, ultimately driving its high pace of innovation.

Commitment to application modernization and digital transformation can be daunting due to the plethora of questions and trends surrounding the process, often leading to analysis paralysis. Organizations are advised to start small, using a cross-functional team to focus on incremental and iterative progress rather than widespread changes, which can lead to chaos. This approach is supported by behavioral science, which advocates the "pick one and go" method. Emphasizing minimally viable changes (MVC) can help organizations release updates faster and reduce the risk of errors, particularly with legacy software. Mastering continuous delivery and deployment (CD) is crucial, as it enables quicker feature releases while maintaining system stability and security. By documenting and automating deployment pipelines, organizations can improve efficiency, as highlighted by Gary Gruver in his book on DevOps. The journey requires both cultural and technological changes, as exemplified by Ask Media Group's successful modernization with microservices, containers, and Kubernetes.

GitLab is proposing to merge its two separate repositories, gitlab-ce and gitlab-ee, into a single repository to streamline development processes and enhance efficiency. Currently, maintaining these repositories separately for open-source and proprietary code leads to duplicated work, pipeline failures, and conflicts during releases, resulting in significant delays and wasted engineering time. Despite past efforts to automate merges and reduce conflicts, challenges persist due to the increasing volume of commits and complex merge scenarios. The proposed unified repository will house all frontend assets as open source under the MIT license, while proprietary backend code will reside in a dedicated directory. This change aims to simplify feature development and documentation, although it may introduce minor inconveniences for users cloning the source and managing database tables. GitLab invites feedback on the proposal to ensure the best approach to reducing inefficiencies while maintaining the platform's integrity and success.

Since the beginning of the year, the DevOps industry has experienced notable consolidation, highlighted by acquisitions such as Travis CI by Idera and Shippable by JFrog, reflecting a maturation phase where tool consolidation naturally occurs. Continuous integration (CI) remains crucial for accelerating code deployment, especially as enterprises increasingly adopt cloud-native approaches to maintain a competitive edge. Concerns arise regarding the stability of CI partners amidst these changes, prompting GitLab to reassure users of its ongoing commitment and growth, including plans for an IPO by November 2020. GitLab positions itself as a versatile CI/CD solution compatible with GitHub and invites developers to use its platform for comprehensive workflow management. The company also reaches out to former Travis CI employees affected by recent layoffs, offering opportunities within its team and acknowledging the transitional challenges that often accompany industry acquisitions.

Jason Yavorska, the product manager for the Release stage at GitLab, introduces a new feature in GitLab 11.8 that allows users to select popular Pages templates directly from the new project setup screen, simplifying the process of setting up a site. This change eliminates the need to fork an existing template, letting users start projects swiftly with bundled options, although the traditional method remains available for other templates. Yavorska, despite being a product manager, contributed to this feature as a hobbyist programmer, finding the coding process straightforward but navigating the review process more challenging. He expresses pride in the collaborative effort and encourages others to contribute to open source projects, offering his support on Twitter for first-time contributors. The post provides a detailed guide on setting up a site using the Hugo template, including necessary edits and pipeline initiation, and offers advice on further customization and resources for enhancing the site with Hugo themes.

As the new year progresses, the challenge of maintaining personal and professional commitments becomes apparent, paralleling the difficulties seen in stalled digital transformation efforts. Emphasizing the importance of commitment to processes rather than just goals, GitLab illustrates its success by adopting an all-remote work model and a consistent monthly release cycle, leading to the development of a unified application for the DevOps lifecycle. GitLab's commitment strategy involves asynchronous communication and comprehensive documentation, enabling collaboration across global teams and achieving faster feedback loops. The company encourages others to embrace similar commitments in software modernization, faster cycle times, and more secure applications, offering support through upcoming blog posts, guides, and community engagement under the #JustCommit initiative.

In 2016, the Verizon Connect Telematics Container Cloud Platform team faced challenges with lengthy data center builds and manual processes due to their reliance on legacy systems and disparate tools like BitBucket, Jenkins, and Jira. To improve deployment speed and automation, they transitioned to a microservices architecture and aimed for complete CI/CD, focusing on automation, simplification, and avoiding vendor lock-in by using open-source tools. They selected GitLab for its open-source nature, ease of use, and comprehensive features, which replaced multiple systems and provided a unified solution for code review, CI/CD, issue tracking, and more. This transition allowed them to reduce their data center deployment process from 30 days to under eight hours, achieving platform agnosticism and enabling developers to focus on more innovative tasks.

GitLab's infrastructure team manages the largest GitLab instance, with about 3 million users, utilizing PostgreSQL as a critical component to prevent data-loss disasters. Through backup and replication strategies, they address data recovery challenges, exemplified by the recovery of accidentally deleted data using delayed replication. Delayed replication involves applying changes with a time delay to a replica, enabling recovery of data to a specific point in time, such as before a deletion event. This is achieved through PostgreSQL's Point-in-Time Recovery (PITR) and archive recovery, allowing for efficient recovery without the need for a full snapshot restoration, which can be time-consuming. While delayed replication aids in recovering from accidental data loss, it is not a substitute for proper backups, which are essential for addressing more severe incidents like data center failures or corruption. The GitLab team highlights the importance of distinguishing between replication, which maintains database availability and load distribution, and backups, which are crucial for disaster recovery.

GitLab's UX design team has developed a new Security Analyst Persona, named Sam, to better understand and address the needs of security professionals. This initiative stemmed from interviews that revealed Security Analysts' roles as generalists, handling various tasks under security, and their desire for streamlined workflows to monitor and address vulnerabilities more efficiently. A key finding was their preference for comprehensive tools that consolidate monitoring tasks, as well as their motivation to be proactive in identifying potential threats. Frustrations include limited resources and organizational red tape that hinder timely issue resolution. In response, GitLab has introduced features like the Group-level Security Dashboard to empower security professionals by providing a unified view of project vulnerabilities and enabling immediate action. The persona development is part of GitLab's ongoing effort to create tailored solutions for different professional roles, with further enhancements planned as part of their product roadmap.

The text discusses the process of cleaning up Git commit histories to maintain a tidy and coherent version control record. It highlights the common practice in open source projects of requesting contributors to clean up their merge or pull requests to avoid cluttering the Git history with trivial commits like "fix typo." The author explains a method using Git commands such as `git reset --soft`, `git commit --fixup`, and `git rebase -i --autosquash` to consolidate multiple commits into a more streamlined set. This involves reverting unnecessary commits, creating fixup commits, and performing an interactive rebase to merge related changes. The importance of using `git push --force` cautiously when updating remote repositories is emphasized, as improper use can lead to serious issues. The author also mentions the alternative approach of using `git commit --amend` to incorporate changes into the last commit, thus reducing the number of new commits needed.

The Donatinator is an open-source platform developed to help small charities and non-profits easily accept one-off and recurring donations online without incurring high costs, except for unavoidable credit card processing fees. Inspired by difficulties faced by a mothers' support group in accepting donations, the creator embarked on developing this tool to provide a free and accessible solution for organizations worldwide. The platform, hosted on GitLab, aligns with open-source values by allowing users to download, modify, and contribute to the project, while its basic installation remains within the free tier of various hosting providers. Despite the initial charity opting for an existing donor platform, the developer continues to enhance The Donatinator, calling for community contributions, sponsorships, and user engagement to foster its growth and ensure its sustainability. The aim is to provide a practical solution for charities, especially those operated by non-technical volunteers, to maintain their vital services without financial strain.

Forrest Brazeal, an experienced cloud architect and AWS Serverless Hero, outlines a comprehensive guide on deploying serverless applications using AWS SAM and GitLab CI/CD. He emphasizes the importance of a structured approach to deploying serverless applications across multiple AWS accounts to maintain security and separation of environments like development, staging, and production. The guide details setting up cross-account IAM roles, creating an S3 bucket for CI artifacts, and configuring the GitLab CI/CD pipeline, which includes stages for testing, building, and deploying serverless applications. Brazeal highlights the use of dynamic feature branch deployments and Review Apps for efficient parallel development, as well as the need for manual intervention before code release into production. The article provides a step-by-step approach to automating AWS deployments, demonstrating how to integrate tests, builds, and deployments into a GitLab repository to securely roll out SAM-defined serverless applications. Interested readers are encouraged to try the process themselves using a sample AWS News application provided in the GitLab repository.