Petes Linkedin Blog

We strongly recommend that all GitLab installations be upgraded to one of these versions immediately. Note regarding Runner registration token disclosure: This update will reset runner registration tokens for your group and projects. If you use an automated process (scripts that encode the value of the registration token) to register runners, this update will break that process. However, it should have no affect on previously registered runners. If applicable to your processes, your administrator may choose to save a back-up of your existing tokens which can later help identify potentially malicious registration tokens or rogue runners. For example, if an unauthorized actor tries to register a runner using one of the revoked tokens, knowing that value will help admins monitor that type of activity. Today we are releasing versions 14.8.2, 14.7.4, and 14.6.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). Please note, this critical release will also serve as our monthly...

Today we are releasing version 14.8.1 for GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in this month's 14.8 release and prior versions. GitLab Community Edition and Enterprise Edition Fix toolbar buttons in Markdown field Revert: Link by commit and name for pipeline Stop backup files from requiring directories to exist when skipped Allow assigning users with private profiles with quick-actions Important notes on upgrading This version does not include any new migrations, and for multi-node deployments, should not require any downtime . Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates . Updating To update, check out our update page . GitLab subscriptions Access to GitLab Premium and Ultimate features is ...

Software requirements change over time. Customers request more features and the application needs to scale well to meet user demands. As software grows in size, so does its complexity, to the point where we might decide that it's time to split the project up into smaller, cohesive components. As we proceed to tackle this complexity we want to ensure that our CI/CD pipelines continue to validate that all the pieces work correctly together. There are two typical paths to splitting up software projects: Isolating independent modules within the same repository : For example, separating the UI from the backend, the documentation from code, or extracting code into independent packages. Extracting code into a separate repository : For example, extracting some generic logic into a library, or creating independent microservices. When we pick a path for splitting up the project, we should also adapt the CI/CD pipeline to match. For the first path, GitLab CI/CD provides parent-child p...

Today, we are excited to announce the release of GitLab 14.8 with new SSH key types , security approval policies , pipeline editor autocomplete , impersonation audit events , and much more! These are just a few highlights from the 25+ improvements in this release. Read on to check out all of the great updates below. To preview what's coming in next month’s release, check out our Upcoming Releases page , which includes our 14.9 release kickoff video. Join us for an upcoming event This month's Most Valuable Person ( MVP ) is Piotr Stankowski Beginning in 14.5, Piotr worked closely with both product and UX to develop a solution that allowed users the flexibility to create custom templates for their merge commits . In 14.6, he followed up by introducing the same variable-based templates for squash commits , dramatically improving the experience for the various preferences teams have for squashing commits. In GitLab 14.8, Piotr continued to build upon his improvements to ...