Petes Linkedin Blog

The DevOps era began with a big idea – dissolve silos to deliver better software, faster. In the transition from classic software paradigms, DIY DevOps toolchains were built with parts that were never designed to work together. That DIY DevOps era left many trapped in new silos, without visibility, and mired in maintenance. Business outcomes suffered as the potential of DevOps was never fully realized. The next iteration of DevOps There is a better way to build software. GitLab 14 delivers modern DevOps with a complete DevOps platform, for a streamlined experience that unleashes the power of DevOps. Over the past year, GitLab has shipped advanced DevOps platform capabilities that enable any team to build and deliver software with velocity, trust, and visibility – no matter their size, industry, or location. With enhancements across the software development lifecycle, GitLab has placed strongly in several market reports across a broad range of areas from Enterprise Agile Planning an...

We recently discovered a Usage Ping configuration bug for self-managed instances and have since published a patch release to fix the bug. The issue affects the ability to disable Usage Ping for self-managed GitLab via text configuration files, resulting in the collection and transmission of Usage Ping events from the instance. This bug affects any instance running GitLab version 9.3 to version 13.12.3, and was patched in 13.12.4 . What does this mean for existing users? This issue does not affect customers who have disabled Usage Ping via the user interface or any users of our SaaS product. You can check your instance configuration settings to see if this issue may have affected you. We’ve published more detailed instructions here . What should I do? Since we do not collect any configuration data from your instance, we have no way to detect if you unintentionally shared data with GitLab. Out of an abundance of caution, we ask that you fill out this form if you suspect that Usa...

Today we are releasing version 13.12.5 for GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in this month's 13.12 release and prior versions. GitLab Community Edition and Enterprise Edition Available in GitLab Free, Premium, and Ultimate: Only update required instance ci template when the parameter is present Fix Password expired error on git fetch via SSH for LDAP user Advanced Search Settings page does not load if the ES url is unreachable 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...

CI/CD pipelines are the preeminent solution to mitigate potential risks while integrating code changes into the repository. CI/CD pipelines help isolate the impact of potential errors, making it easier to fix them. Top that with a tool that provides effective visibility into the running tasks and there you have a recipe for success. Since the primary purpose of CI/CD pipelines is to speed up the development process and provide value to the end user faster, there's always room to make the process more efficient. This blog post unpacks some strategies that can help you get the most out of your pipeline definition in GitLab CI. How Directed Acyclic Graphs (DAG) enable concurrent pipelines By using the "Needs" keyword you can define dependencies for jobs that need to be used from previous stages. In a basic-pipeline structure, all the jobs in a particular stage run concurrently and the jobs in the subsequent stage have to wait on those to finish to get started. This con...

GitLab uses a GPG key to sign official Gitlab Runner packages. We recently became aware of an instance where this key and other tokens used to distribute official Gitlab Runner packages and binaries were not secured according to GitLab’s security policies. We have not found any evidence of unauthorized modification of the packages or access to the services storing them. Our team has audited and investigated integrity hashes, bucket logs and versioning, and pipeline history and concluded that the unauthorized modification of any packages is exceedingly unlikely. Out of an abundance of caution, the GPG key used for release signing and verification has been rotated along with all other tokens that were improperly secured. If you use GitLab.com shared runners, this does not impact you. As of June 8, 2021 the old key used for the package signing, with the fingerprint 3018 3AC2 C4E2 3A40 9EFB E705 9CE4 5ABC 8807 21D4 , has been revoked. The GPG fingerprint of the new key is 09E5 7083 F3...

Last year I wrote about how the Quality Engineering Enablement team was building up the performance testing of GitLab with the GitLab Performance Tool (GPT) . Last year, the biggest challenge with performance testing wasn't so much the testing but rather setting up the right large scale GitLab environments to test against. Like any server application, deploying at scale is challenging. That's why we built another toolkit that automates the deployment of GitLab at scale: The GitLab Environment Toolkit (GET) . GitLab Environment Toolkit logo Internally called the "Performance Environment Builder" (PEB), GET grew alongside GPT as we continued to expand our performance testing efforts. Over time we built a toolkit that was quite capable in its own right of deploying GitLab at scale, which is why it started to gain attention internally from other teams and then even from some customers. Soon we realized we built something worth sharing. The Quality Engineering Enabl...

Today we are releasing version 13.12.4 for GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in this month's 13.12 release and prior versions. GitLab Community Edition and Enterprise Edition Available in GitLab Free, Premium, and Ultimate: Fix double render in project's git URL redirect Fix MR diff compare with previous version Add alias method usage_ping_enabled? Do not show Praefect deprecation if Praefect is disabled Update Mattermost to 5.34.4 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 subscripti...