<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GitLab on iAutomate</title>
    <link>/categories/gitlab/</link>
    <description>Recent content in GitLab on iAutomate</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 27 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="/categories/gitlab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Untapping Infrastructure Registry in GitLab – Part 1</title>
      <link>/blog/untapping-infrastructure-registry-in-gitlab-part-1/</link>
      <pubDate>Thu, 27 Oct 2022 00:00:00 +0000</pubDate>
      
      <guid>/blog/untapping-infrastructure-registry-in-gitlab-part-1/</guid>
      <description>Introduction Yesterday I spent a few hours in Infrastructure Registry for my learning. Oh, well, I am not impressed with the implementation work. But I still love the feature. So, here is the blog post to get started.
Prerequisites  Azure Account.  Refer here for free access (12 Months)   GitLab Account.  Set up your own GitLab instance    Requirement  Create a Terraform module Publish to Infrastructure Registry Consume the module to create Azure resources  Solution  Note: For now, let us ignore the quality of the project scaffolding, security, code scanning, process, and protocols.</description>
    </item>
    
    <item>
      <title>Generate Dynamic Pipeline for folder-specific changes in GitLab</title>
      <link>/blog/generate-dynamic-pipeline-for-folder-specific-changes-in-gitlab/</link>
      <pubDate>Wed, 31 Aug 2022 00:00:00 +0000</pubDate>
      
      <guid>/blog/generate-dynamic-pipeline-for-folder-specific-changes-in-gitlab/</guid>
      <description>Introduction As a DevSecOps focal, I get exciting tasks. Of late, I was battling with mono and multi-repositories. It&amp;rsquo;s easy to convince many, but few won&amp;rsquo;t agree to the project scaffolding change. So, we need to identify the best possible way. I am sure this is not a thin-on-the-ground requirement. Yes, you may need this trick to compromise the team who doesn&amp;rsquo;t wish to go for the mono to multi repository.</description>
    </item>
    
    <item>
      <title>Publish Pester Test Results in GitLab CI</title>
      <link>/blog/publish-pester-test-results-in-gitlab-ci/</link>
      <pubDate>Tue, 23 Aug 2022 00:00:00 +0000</pubDate>
      
      <guid>/blog/publish-pester-test-results-in-gitlab-ci/</guid>
      <description>Introduction I wasn’t sure about the steps to publish the Pester test results in GitLab CI. So, I continued to search over the internet, and as you all know, the search teaches many things. I got many valuable tips and tricks, and here is my version that may help a few.
Requirement  Publish the Pester test results as shown below. Consider using the PowerShell script analyzer in the pipeline.  Solution  .</description>
    </item>
    
  </channel>
</rss>
