ToolUp Tuesday - #7
In this episode of ToolUp Tuesday, Chris and Matt take their Go-based microservices and package them as Docker container images for the first time. They walk through creating Dockerfiles, setting up GitHub Actions workflows to build and push images, and publishing to GitHub Packages container registry using the built-in GITHUB_TOKEN for authentication. Along the way they discuss container fundamentals — the difference between images and containers, why containers solve the “works on my machine” problem, and how to use environment variables in workflows for clean, maintainable CI/CD pipelines. The episode also covers managing container image versions and permissions within a GitHub organization.
Related Content
Using GitHub Actions to summarise your Go tests
GitHub recently posted about a new GitHub Action that can be used to summarise your test results. The action is called test-summary/action, available at github.com/test-summary/action. There are several examples on how to use the action at github.com/test-summary/examples. However, there were no examples on how to use this with Go. I contributed a pull request which showed how to achieve this. In this post, I will show how to use the action with Go.
Tales from the Real World - Shift Left your Performance Tests
Performance testing has traditionally lived in high-fidelity pre-production environments — but by the time you find a performance issue that late in the cycle, the cost to fix it is already compounding. In this episode, Chris is joined by HariKrishnan, Cloud Transformation Consultant, to explore a practical shift-left approach to performance testing. Hari shares real-world experience identifying the categories of performance issues that can be reproduced locally or in CI pipelines using tools like Gatling and Docker, reducing MTTR and avoiding the environment time-sharing bottlenecks that slow teams down.
Discussing the Cloud with Chris GitHub Actions Usage
Cloud with ChrisChris is joined by Karl Cooke (IrishTechie) for a live deep-dive into the GitHub Actions workflows powering CloudWithChris.com. They explore why GitHub was chosen over Azure DevOps, walk through a real-world CI/CD pipeline for a Hugo static site deployed to Azure Blob Storage with CDN purging, and examine how to manage secrets and approvals using GitHub Environments. The session also covers linting Markdown with GitHub Super Linter, early thinking on Playwright-based UI tests, the security considerations around third-party actions from the marketplace, and building a custom .NET GitHub Action for content cross-posting.