phongn opened a new pull request, #469: URL: https://github.com/apache/trafficserver-ci/pull/469
Nothing currently builds the Dockerfiles in this repository until someone does it by hand, so a change that breaks an image is only discovered when that image is next rebuilt. That is also how images quietly rot — the Jenkins jobs for `fedora:40`, `fedora:41` and `ubuntu:23.04` have been failing for months because their distributions went EOL and nothing was watching. This adds a workflow that builds the images from their Dockerfiles and smoke-tests the result. **Nothing is pushed to the registry**; publishing stays a manual step. Starting with `fedora44` and `ubuntu2604` as the two newest images. Covering another one means adding it to the matrix and to the two `paths` filters, so the workflow only runs for images it actually builds. ### Notes for review - **Disk space.** Hosted runners leave roughly 14G free, which is not enough for `fedora44` — it builds BoringSSL, Go, Rust and the HTTP/3 tools from source. The first step reclaims about 25G by removing preinstalled toolchains we don't use. This is the part most likely to need tuning once we see a real run. - **No third-party actions.** Only `actions/checkout`, so nothing here needs an allowed-actions exception beyond what apache/trafficserver already uses. - **Weekly schedule.** Base images and package repositories drift independently of this repo; that is exactly what took the fedora:40 and fedora:41 jobs down. A Monday run surfaces it instead of leaving it for whoever opens the next PR. - **Permissions.** `contents: read`, and superseded runs for the same PR are cancelled. - This is the first workflow defined in this repo's tree. Actions is clearly enabled here (Copilot review runs fine), but if INFRA has an allowed-actions policy on `apache/trafficserver-ci` that I can't read, `actions/checkout` may need to be confirmed. ### Not included Layer caching. Every run rebuilds from scratch, which is slow but predictable. Worth adding once we know the real build times, and worth being careful about given the 10G per-repo cache limit and the size of these images. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
