Quantisan
Feature: exclude architectures
#238 revealed a blind spot in the exclusion code: architectures. This PR refactors & reorganizes some code and fixes that. It replaces the config/distro-architectures subsystem with the more generalized exclusion mechanism.
The only slightly tricky part is that for our variant generation & exclusion code, it makes sense to have a separate variant for each architecture. However, when we generate the manifest file (that tells the Docker Official Image folks what images to build from which dirs in this repo), we need to combine variants that only vary by architecture. So that's what this PR does.
Fixes #238
I'm still working on this. I dove into spec-based generative testing, but I think I'm going to crawl back out of that rabbit hole for one of the fns I started implementing it for. I will have some generative testing coming up though. :)
I'm making progress on this again. It required getting the test.chuck library running under Babashka, which required changes to Babashka itself, the instaparse pod, and test.chuck (😅) but I now have it generating test inputs from regexes. Getting these generators right was really giving me trouble, but test.chuck's string-from-regex generator is awesome.
Additional commits coming soon!
Once this lands we'll start publishing arm64 alpine variants for Java 21+!
Thanks! I’m on the road. Will be back at work MondayOn Apr 24, 2025, at 2:18, Wes Morgan @.***> wrote: cap10morgan left a comment (Quantisan/docker-clojure#240) Once this lands we'll start publishing arm64 alpine variants for Java 21+!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Focusing on all-tags-test as an arbitrary example, I found myself shuffling it a bit for my own understanding. Sharing for a diff perspective:
(deftest all-tags-test
(testing "Generates specific tag format: <base-alias>-<jdk>-<build-tool>"
(let [;; --- Shared configuration for these test scenarios ---
build-tool "tools-deps"
build-tool-version "1.11.1.1155"
;; --- Define the scenarios we want to test ---
;; Each map represents a specific context based on JDK version.
test-scenarios [
{:jdk 11
:base-image "eclipse-temurin" ; Default base for pre-JDK21
:distro :ubuntu/jammy ; Default distro for pre-JDK21
:desc "JDK 11 (pre-JDK21 defaults)"}
{:jdk 17
:base-image "eclipse-temurin" ; Default base for pre-JDK21
:distro :ubuntu/jammy ; Default distro for pre-JDK21
:desc "JDK 17 (pre-JDK21 defaults)"}
{:jdk 21
:base-image "debian" ; Default base for JDK21+
:distro :debian/bookworm ; Default distro for JDK21+
:desc "JDK 21 (post-JDK21 defaults)"}]
;; --- Define the function to generate the expected tag for this specific format ---
;; This format omits the default distro and the build tool version.
;; It uses "temurin" as the base image alias even if the base image is "debian".
generate-expected-tag (fn [jdk build-tool]
(str "temurin-" jdk "-" build-tool))]
;; --- Iterate through scenarios and perform assertions ---
(doseq [{:keys [jdk base-image distro desc]} test-scenarios]
(testing desc
(let [variant {:base-image base-image
:jdk-version jdk
:distro distro ; This is the default, so it should be omitted in the generated tag
:build-tool build-tool
:build-tool-version build-tool-version}
expected-tag (generate-expected-tag jdk build-tool)
all-generated-tags (set (all-tags variant))]
(is (contains? all-generated-tags expected-tag)
(str "Set of tags should contain '" expected-tag "'. "
"Variant tested: " (pr-str variant) ". "
"All generated tags: " (pr-str all-generated-tags)))))))))