Petes Linkedin Blog

Today we are releasing version 14.1.6 for GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in this month's 14.1 release and prior versions. GitLab Community Edition and Enterprise Edition Derive virtual storage's filesystem id from its name Fix Elastic::MigrationWorker current_migration 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 granted by a paid subscription . Alternatively, sign up for GitLab.com to use GitLab's own infrastructure....

Today we are releasing version 14.0.11 GitLab Community Edition and Enterprise Edition. This version resolves a number of regressions and bugs in the 14.0 release and prior versions. GitLab Community Edition and Enterprise Edition Derive virtual storage's filesystem id from its name Fix Elastic::MigrationWorker current_migration Important notes on upgrading These versions do 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 granted by a paid subscription . Alternatively, sign up for GitLab.com to use GitLab's own infrastructure. from GitLab ...

Configuring Sidekiq in your own deployment of GitLab is a little complicated, but entirely possible. In this blog post, we share how to set up Sidekiq for GitLab in special cases and at a large scale by sharing some exmaples that may be useful to you. Why consider special configuration? While Sidekiq (both in general, and in a GitLab deployment) will usually just work most of the time, there can be some sharp edges and limits. Raw scale is a clear and obvious driver for needing to take action, and although it may be fine to simply scale out multiple Sidekiq nodes each listening to all the queues, at some point: The uniqueness of workload distribution and job characteristics may require dedicated workers, either sharded on job attributes (as for GitLab.com), or specific workers (based on your workloads), or Simple saturation on Redis means you need to listen to fewer queues [We share all we learned about configuring Sidekiq on GitLab.com ] Example: Demo systems In early 2021, ...

If every company is a software company, how do you stand out from the crowd when it comes to attracting developer talent and filling DevOps jobs? There’s a well-known, and worldwide, shortage of software developers, especially those with expertise in DevOps. Worse still, demand for those roles is accelerating rapidly: The US Bureau of Labor Statistics predicts employment opportunities for devs and testers will increase 22% between 2020 and 2030 . That growth rate means nearly 190,000 net new developer/QA/test jobs will be opening each year, according to the BLS. That’s all a long way of saying things are tough out there. Organizations looking to expand, or even just maintain, their DevOps jobs momentum have to find unique ways to stand out from the crowd because, as many surveys have shown , salary alone is often insufficient to both attract and retain developer talent. Elevating your DevOps skills? Join us at Commit at KubeCon - Oct. 11! Here are 3 ways organizations can create an...

Effectively communicating a customer’s private needs to product teams is essential to a product’s success, but it can be a tricky undertaking. Teams can face several challenges in communicating and tracking customers' requests, including protecting customer confidentiality, tracking priority and progress, and making sure the product team is getting actionable feedback that can be incorporated into product milestones. This blog post shares GitLab's best practices and lessons learned, as well as a video conversation between GitLab CEO Sid Sijbrandij and Fleet CEO Mike McNeil . In line with GitLab's open core model and transparency value , our product roadmap is public and the product team uses public issue trackers for feature requests and to plan the work. Because the issues are public, customers and community members can see how the product team works, what direction we are headed, and what the priorities are. Contributors can even decide to create a feature themselve...

Today, we are excited to announce the release of GitLab 14.3 with project-level security scan execution policies , next generation SAST to reduce Ruby false positives , group-level permissions for protected environments , group access for the GitLab Kubernetes Agent , and much more! These are just a few highlights from the 40+ 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.4 release kickoff video. Join us for an upcoming event This month's Most Valuable Person ( MVP ) is feistel @feistel started contributing to GitLab Pages in September 2020. In the last 4 months, they have made continuous contributions to improve Pages by adding features, fixing bugs, and helping us clear the Pages issues backlog. In 14.3, they took the initiative to work on some of the release group deliverable issues for the milestone , allowing us to fo...