<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure on Will Arroyo</title><link>https://blog.warroyo.com/tags/azure/</link><description>Recent content in Azure on Will Arroyo</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Will Arroyo</copyright><lastBuildDate>Wed, 28 Dec 2022 21:26:22 +0000</lastBuildDate><atom:link href="https://blog.warroyo.com/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>Integrating TAP with Azure DevOps Pipelines</title><link>https://blog.warroyo.com/posts/integrating-tap-with-ado-pipelines/</link><pubDate>Wed, 28 Dec 2022 21:26:22 +0000</pubDate><guid>https://blog.warroyo.com/posts/integrating-tap-with-ado-pipelines/</guid><description>&lt;p&gt;TAP has an OOTB source code testing capability that makes use of &lt;a href="https://tekton.dev/docs/pipelines/pipelines/" target="_blank" rel="noreferrer"&gt;Tekton pipelines&lt;/a&gt; to execute tests based on your workload types. However, many organizations have already implemented their testing processes in another tool like Jenkins or Azure DevOps (ADO). As of TAP 1.3, you can &lt;a href="https://docs.vmware.com/en/VMware-Tanzu-Application-Platform/1.3/tap/GUID-scc-ootb-supply-chain-testing-with-jenkins.html?hWord=N4IghgNiBcIFYFMB2BrAlkgziAvkA" target="_blank" rel="noreferrer"&gt;natively use Jenkins&lt;/a&gt; for your source testing in the TAP supply chain. In talking with several customers and co-workers it was apparent that integrating with ADO would be very useful. In this post, we will walk through the steps to get the TAP source code testing capability working with Azure DevOps pipelines.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blog.warroyo.com/posts/integrating-tap-with-ado-pipelines/featured.png"/></item></channel></rss>