Running GitHub Actions on my own computer: what ubuntu-latest was quietly doing for me16 October 2026
I moved my GitHub Actions jobs to a self-hosted runner in Docker to save minutes. Jobs first failed, then got slower, because every job downloaded what GitHub's hosted image already has. Putting those tools in the runner image brought a deploy from 2:00 to 1:28.
End to end automation of site deployment with Claude27 September 2026
Automating website deployment with AI: I tell Claude which site to add or update and what to change, and everything after that is automatic, except my review of the pull request. Claude gets no Cloudflare credentials; it prepares one PR with config, custom domain and images, and GitHub Actions and Cloudflare Workers Builds deploy it after the merge.
AZ-400: Built & pushed an artifact in 30 minutes, but spent 2 hours setting up SonarQube16 May 2026
Integrating SonarQube (via SonarCloud) into a GitHub Actions pipeline: the quirks that ate two hours (host-URL validation, version-specific scanner behavior, global-tool install issues), the fix (pinning an older SonarScanner for .NET), and how easy Dependabot + CodeQL were by comparison.
Yesterday I created a build and push artifact CI/CD pipeline for AZ-400 practise in Azure DevOps!16 May 2026
Building a reusable Azure DevOps YAML pipeline for a small .NET helper library: AI-assisted (Aider + Qwen2.5) unit tests, automated SemVer NuGet packaging to GitHub Packages, restore caching, a dotnet format style gate, and the Cache@2 quirk that needed a manual mkdir to fix.
Checkout my new website and live text analysis demo!7 May 2026
The build log for koorevaar.com itself: three evenings from buying the domain to a portfolio built with Aider+Qwen2.5, GitHub Actions pipelines, and a Terraform-deployed Azure Container Apps text-analysis demo behind a Cloudflare Worker + phi3:mini.
AZ-400 Practice - week 3: Complete Blue/Green + Canary CI/CD on AKS2 May 2026
Week 3 of an AZ-400 side project: a full Terraform + AKS + Traefik pipeline covering infrastructure, blue/green + canary deployment, and teardown — with real execution times for each stage, down to seconds for a blue/green traffic switch.
Another update about my AZ-400 practice project!25 April 2026
Adding a detect-language endpoint to the sentiment API, backed by AI-assisted unit tests (Aider + Qwen) that also run on main, a feature-branch flow set up for blue-green then canary, and a Flask route-ordering gotcha (routes must be defined before the blocking app.run() call).
AZ-400: Sentiment API live on AKS via cross-subscription Azure DevOps pipeline19 April 2026
The sentiment API goes live via a real two-pipeline, cross-subscription Azure DevOps setup: Terraform cluster creation feeding a second deploy pipeline through cross-pipeline artifact passing, arm64/amd64 cost-split nodepools, end-to-end deploy in 2 minutes.