<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Self hosted agent on Erwin Staal</title>
    <link>https://staal-it.nl/tags/self-hosted-agent/</link>
    <description>Recent content in Self hosted agent on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sun, 25 Jul 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/self-hosted-agent/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automatically renew the image used in an Azure DevOps private agent</title>
      <link>https://staal-it.nl/posts/automatically-renew-private-agent-images/</link>
      <pubDate>Sun, 25 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/automatically-renew-private-agent-images/</guid>
      <description>&lt;p&gt;In a previous post, I wrote about creating your own hosted Build and Release agents in Azure DevOps. That process could be improved by regenerating the VM image, for example, every month. By doing that, you stay up-to-date with both the latest versions of all the tools installed as well as with security patches. This post will describe how to do that using an Azure DevOps pipeline which will be triggered monthly.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
