GitLab is a collaboration tool that helps users:

• Maintain source/version control
• Improve visibility of projects
• Store packages and containers
• Plan work and manage portfolios and projects
• Ensure compliance
• Maintain security

GitLab supports a wide variety of clients, provides maximum flexibility in configuration, and offers many features. The ultimate tier features are included in the license. Some features may not be enabled yet.

Campus License

We have a GitLab for Campuses license that includes the ultimate tier features. The license is centrally funded and a stable Campus resource. We have many opportunities to continue to grow this service. We recommend this resources to all those eligible at UW-Madison. Let us know if you want to meet, discuss your future needs, and ensure your group is set up for success with GitLab.

Can You Use GitLab?

See also DoIT Shared Tools - GitLab - Service Eligibility and DoIT Shared Tools - GitLab - How-to Login.

By default all users receive 4 personal projects. If you are performing work as a service or project team, you should request a GitLab group. 

Need a GitLab Group or Have Questions?

If you need a GitLab group or want to know more about the current service offering(s), please contact the Shared Tools team to schedule a needs analysis.

Maintenance and Patching

Maintenance Window

The standard GitLab maintenance window is Tuesday 10:00-11:59 pm.  During this time, the service may be unavailable. All outages are listed on outages.doit.wisc.edu. 

Update and Patching Schedule

The standard scheduled for updating our GitLab instance is:

Week 1 Patching - The latest patch update released by GitLab is installed on the Tuesday of the first week of each month.

Week 3 Minor Version update - The Shared Tools GitLab instance is typically 1-2 minor versions behind the latest GitLab release, which comes out each month. 

Emergency Security Patches

Security patches released by GitLab between minor version updates are evaluated by the Shared Tools team for level of risk and may be installed on an emergency basis. 

Examples

Emergency (ASAP): An exploit that lets an unauthenticated user gain access to GitLab

Emergency (ASAP after hours): A critical vulnerability that only an authenticated user could exploit