Posts

GitLab empowers Minorities in Tech with new employee resource group

Image
This is the final part of our three-part series on diversity, inclusion and belonging. Part one focuses on GitLab's diversity goals and efforts to date. Part two examines some of the challenges with diversity, inclusion, and belonging in the tech industry as a whole, and shares some recommendations on how to overcome them. People of color are more likely than any other group to voluntarily leave their jobs in the tech industry due to persistent unfairness in the workplace – whether that is due to stereotyping and discrimination, or because opportunities for career advancement are lacking. In the Tech Leavers Study by the Kapor Center for Social Impact, one-quarter of men and women from underrepresented groups reported experiences of stereotyping in the workplace. “One of the discriminations that I’ve had to deal with outright is my size and my skin color," says Sharif Bennett , mid-market account executive at GitLab. “I’m about 6'3 and some would relay back to me tha...

Artifact and job meta data expiration settings are changing for GitLab.com

Image
To help maintain overall stability and performance for all GitLab users, some changes are coming to GitLab.com effective June 22, 2020. This will directly impact the default retention period for older job metadata as well as enable a default expiration policy for older job artifacts. TL;DR Updating GitLab.com's Job Artifact Expiration Policy What you need to know: Starting June 22, 2020, new job artifacts will immediately default to a 30 day expiration upon creation. Existing artifacts created in the last 12 months will be set to expire 12 months from their creation date. Existing artifacts created more than 12 months ago will have their expiration date set to August 22nd, 2020. For additional details, please see our GitLab.com CI/CD settings documentation . Default archive of jobs on GitLab.com set to 3 months What you need to know: Starting June 22, 2020 jobs older than 12 months will be archived. Starting August 6, 2020 jobs older than 6 months will be archived. ...

What diversity, inclusion, and belonging looks like in the tech industry

Image
This is the second in our three-part series on diversity, inclusion and belonging. Part one focuses on GitLab's goals and efforts to date. It’s no secret that the tech industry has stumbled, struggled, and in some cases outright failed when it comes to building inclusive workplaces where women, people of color, members of the LGBTQ community, and other underrepresented groups are adequately represented. And how can they, when the majority of people working in and leading tech companies are white men? In 2014 several tech companies including Apple, Facebook, and Microsoft, released their first diversity reports, which showed what many people already knew: The majority of tech workers are white and male . "Most times when you are forming a company people tend to gather those that are a lot like them whether it be race, occupation, gender, etc. As a result you take a look at your company start-up just to realize what you have formed is not as diverse as you would like," ...

Notification emails when pipelines are fixed

Image
GitLab can send users a notification when a pipeline fails so that they can respond to the failure quickly. Now, GitLab can also send a notification to inform users when the pipeline has been fixed . This new notification eliminates the need for developers to constantly monitor the status of pipeline builds. This lets developers make better use of their precious time. We are gradually rolling out this feature in order to test it out. During this testing period, users will start getting notifications for fixed pipelines. Example email: To disable the setting for a particular project only: Go to the Project overview page for the project. Click the "bell" (Notification setting) button and select Custom . Uncheck the Fixed pipeline checkbox. To disable the notification for all projects: In the top right, click your user icon and choose Profile . In the top right of the next page, click the "pencil" (Edit Profile) button. On the left, click Notificatio...

Helping organizations build successful design systems

Image
Creating a design system Over the last few years, GitLab has invested in the creation of Pajamas , our living design system. We believe that a design system can help us scale more efficiently by creating a shared vision and language that is used across departments and teams. Now, we're interested in hearing from our community: How can GitLab help you build a successful design system in your own organization? What is a design system A design system is a series of documentation that includes both design practices, as well as frontend guidelines. Live coded demos are included to allow cross-functional teams to easily reuse styles and components in several instances across your product. The underlying principles and guidelines that you develop are what set your design system apart from others. Benefits Design systems provide many benefits to organizations including: Efficiency Product Designers can spend more time solving problems and less time designing (and redesigning) UI c...

Our journey to a more diverse and inclusive workplace

Image
Despite the talent of black leaders, there are glaring disparities in representation of black professionals in positions of power in a number of industries, including in tech. About 5% of tech professionals are African American, and less than 2% of tech executives are African American, according to data from the Harvard Business Review . GitLab is not immune to diversity disparities in leadership. At GitLab, we have zero black or Latinx director-and-above leaders ). Our CEO, Sid Sijbrandij , is committed to fixing this by hiring or promoting internally by 2021, along with a host of other diversity, inclusion, and belonging (DIB) actions that were already in development to make GitLab a more diverse and inclusive company, where everyone feels a sense of belonging. "The past few weeks have reinforced for me the importance of being an ally and taking action to create more diversity within our company," says Sid. "Our executive team believes we can do more to ensure that t...

GitLab Critical Security Release: 13.0.6, 12.10.11, 12.9.10

Image
Today we are releasing versions 13.0.6, 12.10.11, 12.9.10 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases : a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. You can see all of our regular and security release blog posts here . In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is ...