Petes Linkedin Blog

As a software engineer, I spend a significant portion of my day in the Visual Studio code editor. Since I started maintaining the officially supported GitLab VS Code extension , I've developed a few tricks that make me a productive GitLab user. Below, I share eight tips that make my work more efficient and productive, while also introducing you to some of the GitLab contributors who made this tooling happen. 1. Clone GitLab project GitLab contributor Felix Haase recently implemented a feature that lets you clone any GitLab project where you are a member . To clone the project, use the official Git: Clone command and select your GitLab instance. Use the Git: Clone command by selecting the command from the Command Palette . This feature can save you time if you already know the name of the project you want to clone. VS Code lets you filter which project to clone. 2. View MRs and issues It is easy to look through issues and MRs that you created, are assigned to, or are revie...

   This blog post is Unfiltered    A bug when job needs a manual job In 13.12 we fixed a bug that might affect the existing behavior of your pipeline. This blog explains why we had to fix it, the possible impact of this change on your pipeline, and the proposed workaround if you would like to revert this behavior. Background In GitLab CI/CD you can easily configure a job to require manual intervention before it runs. The job gets added to the pipeline, but doesn't run until you click the play button on it. Let's look at a two job pipeline: stages : - stage1 - stage2 job1 : stage : stage1 script : - echo "this is an automatic job" manual_job : stage : stage2 script : - echo "This is a manual job which doesn't start automatically, and the pipeline can complete without it starting." when : manual # This setting turns a job into a manual one This is how it looks when we look at the pipeline graph: Not...

Several years ago, a portfolio manager asked me if he needed to learn about “all the stuff the DevOps people do.” I told him yes, explained why it was worth it to “learn their language,” and discussed how he could extract nuggets of information to help unlock product value. It was good advice at the time, but it didn’t answer the bigger question—“Sure, he should , but should he have to ?” The answer to that question is no. He already had a job—managing a P&L for several products. He shouldn’t have to learn another job just to do that one well. Tools are rarely the solution, but they’re often the problem. At the time, without custom integration, lots of digging, manual translation, and a little bit of luck, there just wasn’t a good way to surface all the information the portfolio manager needed to do his job well. At best, he’d receive batched reports from different tools in his DevOps toolchain, with none of them connected to the tools where decisions were made. So putting on a D...

Hi! I’m Jacie Bandur. I completed GitLab’s CEO Shadow program from 2021-04-26 through 2021-05-07. It was a really enlightening experience. I generally work in Learning and Development and consider myself a lifelong learner. I can’t even explain how much I learned in such a short about of time. I learned a lot about the business. I learned a lot about the product. But learned even more about the importance of iteration in everything we do. Qualifications to Participate I wanted to start this off with touching on qualifications to participate in the program. I am the type of person that has gone through most of my life thinking I’m not qualified for things. I’m not qualified for that job, that promotion, that program. The list goes on and on. When I saw the CEO Shadow program kick off in 2019, I really wanted to participate. I was a little intimidated. Who wouldn’t be, spending 2 weeks with the CEO of any company? But time passed and all the sudden it was 2021 and I had not taken any...

In our just released 2021 Survey, 4300 people told us about their successes and their challenges, but in some ways the biggest takeaway were the signs of a burgeoning DevSecOps maturity model. Somehow, when Covid and DevOps collided, big things started to happen particularly around DevSecOps. Yes, Virginia, there is a DevSecOps More teams are doing DevSecOps than ever before – and doing it well. Fully 72% of security professionals rated their organizations' security efforts as "strong" or "good," a significant increase from 59% the year before. This shows us that investments in security and the cultural shifts from DevOps to DevSecOps are paying off. That's right, we're shifting left Over 70% of security pros said their teams have shifted left and moved security earlier into the development lifecycle. So who's in charge? That's still an open question in this new DevSecOps maturity model. Almost 31% of security pros told us they were the one...

In our just released 2021 Survey, 4300 people told us about their successes and their challenges, but in some ways the biggest takeaway were the signs of a burgeoning DevSecOps maturity model. Somehow, when Covid and DevOps collided, big things started to happen particularly around DevSecOps. Yes, Virginia, there is a DevSecOps More teams are doing DevSecOps than ever before – and doing it well. Fully 72% of security professionals rated their organizations' security efforts as "strong" or "good," a significant increase from 59% the year before. This shows us that investments in security and the cultural shifts from DevOps to DevSecOps are paying off. That's right, we're shifting left Over 70% of security pros said their teams have shifted left and moved security earlier into the development lifecycle. So who's in charge? That's still an open question in this new DevSecOps maturity model. Almost 31% of security pros told us they were the one...

Recently, there has been a massive uptick in abuse of free pipeline minutes available on GitLab.com and on other CI/CD providers to mine cryptocurrencies. In addition to the cost increases, the abuse creates intermittent performance issues for GitLab.com users and requires our teams to work 24x7 to maintain optimal services for our customers and users. To discourage and reduce abuse, starting May 17th, 2021, GitLab will require new free users to provide a valid credit card in order to use shared runners on GitLab.com. However, a user will be able to run pipelines without providing a credit card if they use their own runner and disable shared runners. Although imperfect, we believe this will reduce the abuse. We plan to rollout this change gradually and increase the scope if needed in the following manner. We plan to start with adding the new requirement for new free users created on or after May 17th, 2021. If we continue to see abuse through existing free accounts, we plan to extend...