<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Azure-Devops on DevOps &amp; Rock&#39;N&#39;Roll</title>
    <link>https://artazar.pages.dev/tags/azure-devops/</link>
    <description>Recent content in Azure-Devops on DevOps &amp; Rock&#39;N&#39;Roll</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 15:55:02 +0700</lastBuildDate>
    <atom:link href="https://artazar.pages.dev/tags/azure-devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Azure Pipelines YAML validation: full throttle</title>
      <link>https://artazar.pages.dev/blog/02-azd-pipelines-validation/</link>
      <pubDate>Fri, 29 Sep 2023 00:08:30 +0000</pubDate>
      <guid>https://artazar.pages.dev/blog/02-azd-pipelines-validation/</guid>
      <description>&lt;p&gt;I have been using &lt;a href=&#34;https://azure.microsoft.com/en-us/products/devops/pipelines&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Azure Pipelines&lt;/a&gt; as my primary CI system of choice for few years now, and, while I don&amp;rsquo;t find it perfect, I always feel big power inside its YAML templating and rich API capabilities.&lt;/p&gt;&#xA;&lt;p&gt;This post will be a guide on how to maintain a set of YAML templates for CI pipelines and validate changes to them. The set of YAML templates is commonly placed outside of application repos and are referenced by smaller portions of YAML on the corresponding app repos.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
