<?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 Diogo Gomes</title><link>https://diogogomes.com/tags/devops/</link><description>Recent content in DevOps on Diogo Gomes</description><generator>Hugo</generator><language>en</language><copyright>{year}</copyright><lastBuildDate>Fri, 28 Aug 2026 20:31:00 +0100</lastBuildDate><atom:link href="https://diogogomes.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Running GitHub Actions on Campus: Self-hosted Runners for DETI Students</title><link>https://diogogomes.com/2026/08/28/github-actions-self-hosted-runners-deti/</link><pubDate>Fri, 28 Aug 2026 20:31:00 +0100</pubDate><guid>https://diogogomes.com/2026/08/28/github-actions-self-hosted-runners-deti/</guid><description>&lt;p&gt;GitHub Actions has become a very useful part of our teaching workflow at the Department of Electronics, Telecommunications and Informatics (DETI) of the University of Aveiro. Students can automatically build software, run tests, create Docker images, perform static analysis, and experiment with CI/CD using the same tools they are likely to encounter professionally.&lt;/p&gt;&#10;&lt;p&gt;There is, however, a practical problem when GitHub Actions is used across many courses and student projects: &lt;strong&gt;compute minutes add up quickly&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>