March 2016 Summaries

Since GitLab 8.6, a new feature allows users to mark issues as confidential, which is significant for managing sensitive information like security reports within projects. This feature simplifies the process of reporting and handling security vulnerabilities by allowing reporters to directly mark issues as confidential, making them visible only to project members and assigned individuals, reducing the need for separate public and private issue trackers. The development of this feature highlighted challenges such as managing security concerns and resolving frequent merge conflicts due to the long development period and concurrent feature updates. Despite these challenges, the introduction of automated tests facilitated smoother development, ensuring that potential breakages were identified early. This confidential issues feature is part of a broader set of improvements in GitLab 8.6, which aims to enhance user experience and project management efficiency.

Interest in Security Assertion Markup Language (SAML) among GitLab's enterprise customers has inspired efforts to enhance its integration and documentation within GitLab, aiming to match the functionality offered by LDAP. SAML facilitates secure user authentication and authorization across web domains, enabling Single Sign-On (SSO) without needing to know user details beforehand, as it relies on trusted identity providers. GitLab initially introduced SAML support in version 7.12 through a community contribution, and despite limited updates since, customer interest has spurred further development efforts. A key part of this progress involved reviving the omniauth-saml gem, crucial for SAML integration with GitLab, by taking control from inactive maintainers and releasing version 1.5.0 with new features like Custom Attributes, improved error handling, and bug fixes. This update, along with enhanced documentation, aids users and administrators in better integrating and troubleshooting SAML with GitLab. Looking ahead, plans include leveraging SAML 2.0's capability to retrieve Group Membership information, potentially allowing GitLab Group Memberships to be managed via SAML, paralleling LDAP functionalities and reducing the need for dual setups.

Since its integration into GitLab with version 8.0, GitLab CI has become a key feature of the platform, offering robust continuous integration capabilities with a user-friendly interface. The tool is available for free in both the Community and Enterprise Editions, and supports multi-platform and multi-language environments, allowing users to execute builds on Unix, Windows, and macOS, and work with various programming languages. GitLab CI is notable for its ease of setup, configuration, and use, with features such as parallel builds, real-time logging, and versioned tests through a .gitlab-ci.yml file, which facilitates collaboration and ensures comprehensive testing across all branches. Additionally, it supports continuous delivery and deployment through a variety of job types and environmental variables. The GitLab team encourages users to join their webcast for further insights and to have their questions about GitLab CI answered, highlighting the tool's accessibility and comprehensive functionality.

In a recent webcast, GitLab showcased the new features of GitLab 8.6, with a particular emphasis on enhanced confidentiality, demonstrated by special guest Douwe Maan. The session covered project configuration, user permissions, and new functionalities such as subscribing to a label for better tracking and creating a new branch directly from an issue to streamline workflows. The webcast offered both newcomers and seasoned users valuable insights into utilizing GitLab's functionalities effectively. Participants were encouraged to sign up for the newsletter to stay informed about upcoming webcasts, including a future session focusing on continuous integration with the GitLab CI team.

Funding and maintaining an open-source project like GitLab presents challenges, particularly when it comes to choosing the right licensing model. GitLab has adopted an open-core model with an MIT-licensed Community Edition and a paid Enterprise Edition. The Fair Source license, pioneered by Sourcegraph's Quinn Slack, offers a potential solution by allowing everyone to view the source code and providing free use for a limited number of users, thus combining open-source benefits with commercial viability. GitLab evaluated this model for their Enterprise offering, considering its potential to allow free use up to a certain user threshold before charging. Despite their support for the Fair Source license's principles, GitLab decided against adopting it to avoid market confusion, given their existing free Community Edition and other offerings. Nonetheless, GitLab has incorporated aspects of the Fair Source model by allowing users to modify and publish patch releases under certain licensing conditions.

The post provides an update on recent sponsorships and outlines priorities for future tech diversity sponsorship initiatives. It highlights the company's involvement in events such as Rails Girls and Django Girls, which aim to make technology more accessible to women and girls. Notable events sponsored include Rails Girls Brussels, Django Girls Łódź, and Rails Girls Atlanta, with team members actively participating as mentors. The company is also a Gold Sponsor of the Rails Girls Summer of Code project, which is open for crowd funding support. Additionally, the company focuses on sponsoring events in regions with low opportunities, such as TechParty 2016 in Cuba, to enhance local impact. The post invites proposals for sponsorship and encourages interested parties to engage with their community sponsorship program.

Effective communication is crucial for remote work, and GitLab has implemented a set of guidelines to enhance it. The company emphasizes asynchronous communication, allowing team members to receive and process information at their convenience, which reduces interruptions and respects personal time. Public channels are preferred over private messages to facilitate quicker responses and collective learning. Clarity is maintained by addressing one issue per message, and including links to resources minimizes confusion. Additionally, acknowledging received emails with a simple response, even when no further action is required, ensures closure. Human interaction is encouraged to counteract the impersonal nature of digital communication, and expressing gratitude through dedicated channels fosters a positive work environment. GitLab invites feedback and open use of their communications handbook, underscoring their commitment to collaborative improvement.

GitLab's installation process has significantly improved with the introduction of the omnibus-gitlab packages, which simplify installation and upgrades by providing a single binary package that contains all necessary components. This approach, inspired by Chef Inc.'s Omnibus project, contrasts with traditional Unix design principles by offering a monolithic setup, which has both its advocates and critics. While the omnibus-gitlab packages offer ease and consistency, they also make predetermined decisions about system configurations that may not suit all environments. Despite challenges in maintaining a fast-paced release cycle and ensuring compatibility, these packages have been largely successful in making GitLab accessible and manageable across various platforms. Alternatives like Docker and native packages for Debian and Fedora have been considered, but they present their own challenges in terms of compatibility and maintenance workload. The ongoing development of more customizable and user-friendly installation options aims to further enhance GitLab's accessibility and usability.

GitLab has announced a pricing update for its Enterprise Edition, transitioning from three subscription plans to a single simplified plan without minimum seat requirements, allowing licenses to be purchased per-seat at $39 annually, the same price as the previous Basic Plan. The update introduces Premium Support as an add-on, offering 24/7 emergency support, training workshops, and other services for $9,900 per year plus an additional $99 per seat over 100 seats, capped at $50,000. The pricing change aims to enable more flexibility for customers, allowing them to purchase licenses and additional features individually without raising the basic package's price. Existing contracts will be honored until renewal, with opportunities for early renewal at old pricing, while current Plus subscribers will receive future compatible Products for free. Examples of cost impacts show varied effects on different subscription scenarios, with some users seeing a decrease in costs and others experiencing an increase, particularly those utilizing Premium Support.

GitLab 8.6 introduces improved search performance for PostgreSQL by utilizing trigram indexes, which break text into sequences of three letters and can be used with LIKE and ILIKE conditions without altering existing queries. This enhancement significantly speeds up search queries, such as reducing execution time from 160 milliseconds to 0.2 milliseconds by creating a GIN index with the appropriate operator class gin_trgm_ops. The article also compares the limitations of traditional LIKE queries and full-text search methods in PostgreSQL and MySQL, explaining how trigram indexes offer a more efficient alternative without the complexity of full-text search systems. GitLab has implemented specific changes to ensure compatibility with MySQL, which does not support GIN indexes, by modifying schema handling and query syntax to optimize for PostgreSQL's capabilities. This update underscores the substantial improvements in search query performance and the strategic adaptations made to maintain cross-database compatibility.

A Developer Advocate at GitLab shares their initial experiences and insights after joining the company, highlighting GitLab's user-friendly features and integrated tools. GitLab allows users to host their repositories, including private ones, for free on GitLab.com, eliminating the need for manual installation through its Omnibus tool. The platform adopts unique terminology, such as "merge requests" instead of the traditional "pull requests," which aligns more accurately with Git processes. GitLab's embedded Continuous Integration (CI) enhances software development by running tests automatically with the help of "runners," which can be shared or self-hosted. Additional features like GitLab Pages enable effortless website publishing, while the platform's direction promises more integrated functionalities like automated TODO lists from failed builds and potential built-in chat features. The author plans further articles on migrating to and contributing to GitLab, and encourages engagement through upcoming community events and a webcast about GitLab CI.

The blog post provides a comprehensive guide on setting up GitLab CI for iOS mobile projects, detailing the process from initial setup to triggering builds and managing runners. It emphasizes the benefits of continuous integration (CI) for improving developer productivity and code quality by automatically running tests upon code commits. The post explains the necessary configurations in Xcode, including project and scheme setup, and guides readers through creating a .gitlab-ci.yml file to define build and test stages. It also covers registering and configuring a GitLab Runner to execute these processes and offers advanced tips, such as archiving projects for continuous delivery. The guide assumes basic familiarity with Xcode, GitLab, and Terminal, and includes troubleshooting advice for common issues like provisioning errors and runner management.

Evaluating the productivity of software engineers should focus on consistent progress rather than relying on metrics like commit frequency or velocity, which can be misleading and encourage gaming the system. While commits capture changes at a specific moment and issue trackers with weights or points can provide a sense of workload, neither effectively measures individual productivity. Instead, progress should be assessed by observing both communication and activity, as a productive engineer demonstrates deliberate steps toward problem-solving. Although tools like GitLab offer insight into developer activity through commit analytics, they still fall short of capturing true productivity, prompting ongoing efforts to incorporate more comprehensive analytics. Additionally, GitLab plans to expand its capabilities with future updates and invites feedback on how to enhance its analytics offerings.

GitLab is a comprehensive platform that facilitates project management and collaboration by allowing users to cross-link and reference various elements, thereby enhancing discoverability and reducing duplicate efforts. It emphasizes using issues as the "Single Source of Truth" to maintain updated and centralized information, especially when tasks are handed off to others. Users can format content with GitLab Flavored Markdown and reference related issues, merge requests, or snippets to maintain clarity and connectivity across projects. The platform supports categorization through labels and milestones, helping users track progress and deadlines effectively. GitLab encourages early code reviews with Work in Progress (WIP) merge requests and supports collaborative efforts through @mentions and assignments, ensuring that only one person is responsible for a merge request at a time. By automatically closing issues related to a merge request, GitLab streamlines workflow management, allowing users to focus on subsequent tasks without the need for manual updates. A video tutorial further elucidates the GitLab workflow, guiding users in effectively managing issues and merge requests while utilizing the platform's cross-referencing tools.

GitLab's remote work culture, guided by the Remote Manifesto and detailed in their comprehensive handbook, emphasizes flexibility, transparency, and human connection. Growing from a small team of nine to 54 employees since 2015, GitLab fosters an environment where employees manage their own schedules and are evaluated on their output rather than time logged. The company encourages open communication through public channels to ensure inclusivity and collaboration, and its daily team meetings blend work updates with personal bonding, allowing employees to share aspects of their personal lives, like hobbies and family, in a supportive setting. Despite the lack of physical proximity, GitLab's remote setup promotes a sense of closeness and camaraderie among team members, with support systems in place to rally around those who need encouragement. Additionally, GitLab offers a visiting grant to facilitate face-to-face connections between colleagues, reflecting their commitment to maintaining strong interpersonal relationships within a distributed workforce.

GitLab introduced the "Todos" feature in version 8.5 to help users manage their tasks efficiently without the clutter of numerous email notifications. When a user is assigned an issue, mentioned in a comment, or involved in a merge request, a notification is added to their Todos list, which can be accessed easily from the GitLab interface. Users can mark tasks as done if they take action, but tasks remain pending if resolved by others, ensuring continuous awareness of relevant issues. The feature was developed quickly, leveraging the existing Activity feed system, and underwent significant simplification during its development phase. Despite suggestions for additional functionality, such as tracking Todos on commits, the focus remained on issues and merge requests, where most user actions occur. Naming discussions concluded with "Todos," reflecting its purpose as a reminder system rather than an obligatory task list. The feature has been well-received, highlighting its simplicity and utility in everyday use.

GitLab Inc.'s GitLab Runner offers a cost-effective solution for small startups seeking private CI pipelines, standing out in a landscape where many cloud-based CI providers charge high fees for private projects. This tutorial guides users through establishing a continuous integration workflow using GitLab Runner and its Docker executor, focusing on a sample NodeJS project with two modules, including a PostgreSQL database wrapper. The process involves setting up a .gitlab-ci.yml file to define the build environment, utilizing shared and specific runners, and optimizing build efficiency through caching and parallelization. The tutorial is particularly useful for project managers and developers aiming to implement affordable, test-driven CI solutions tailored to specific project needs.