<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on When Software Attacks!</title><link>https://rikhepworth.com/tags/devops/</link><description>Recent content in Devops on When Software Attacks!</description><generator>Hugo -- gohugo.io</generator><language>en_GB</language><copyright>&amp;copy; Rik Hepworth</copyright><lastBuildDate>Mon, 05 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://rikhepworth.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Importing bicep lint output as test results in Azure DevOps pipelines</title><link>https://rikhepworth.com/posts/importing-bicep-lint-output-as-test-results-in-azure-devops-pipelines/</link><pubDate>Mon, 05 Feb 2024 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/importing-bicep-lint-output-as-test-results-in-azure-devops-pipelines/</guid><description>Bicep is a great improvement over ARM Templates but doesn&amp;rsquo;t remove the need to validate our code at build time. I could continue to use the ARM-TTK and validate the generated template, but bicep has it&amp;rsquo;s own built in rules. Getting build errors in a way that can provide meaningful information in my CI/CD tooling is an interesting challenge.</description></item></channel></rss>