<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dynamic-Pipeline on iAutomate</title>
    <link>/tags/dynamic-pipeline/</link>
    <description>Recent content in Dynamic-Pipeline on iAutomate</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 31 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/dynamic-pipeline/index.xml" rel="self" type="application/rss+xml" />
    <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>
    
  </channel>
</rss>
