<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Events on blog.ehn.nu</title><link>https://blog.ehn.nu/tags/events/</link><description>Recent content in Events on blog.ehn.nu</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Jan 2020 10:59:22 +0000</lastBuildDate><atom:link href="https://blog.ehn.nu/tags/events/index.xml" rel="self" type="application/rss+xml"/><item><title>Event-driven scripting in Kubernetes with Brigade</title><link>https://blog.ehn.nu/2020/01/event-driven-scripting-in-kubernetes-with-brigade/</link><pubDate>Sun, 19 Jan 2020 10:59:22 +0000</pubDate><guid>https://blog.ehn.nu/2020/01/event-driven-scripting-in-kubernetes-with-brigade/</guid><description>&lt;p&gt;In most projects that I’ve been part of, sooner or later the need for various types of automation jobs arises. For example cleaning up old files, moving database backups, running health checks or system tests and so on.&lt;/p&gt;
&lt;p&gt;Historically we’ve implemented these tasks using for example the Windows task scheduler, or through some custom Windows Service app. More recently, we’ve been using Azure Automation jobs for this. Sometimes it can also make sense to use CI/CD automation tools like Azure DevOps for these jobs.&lt;/p&gt;</description></item></channel></rss>