<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitLab Runner on Romano Roth</title><link>https://romanoroth.com/en/tags/gitlab-runner/</link><description>Recent content in GitLab Runner on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 10 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/gitlab-runner/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab DevSecOps Part 2: Creating a Simple Project and Your First Pipeline</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-creating-a-project/</link><pubDate>Wed, 10 Aug 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-creating-a-project/</guid><description>&lt;p>Before we can shift any security checks left, we need a project, a repository, and a pipeline that actually builds something. In Part 2 of our GitLab DevSecOps series, Patrick Steger and I log into GitLab, create a new .NET Core project from a template, and look at the &lt;code>.gitlab-ci.yml&lt;/code> file that GitLab generates for us — including the build and test jobs that will become the foundation for everything we add later.&lt;/p></description></item></channel></rss>