Add reusable builder workflow

[cdce8p]

Followup to #326 (comment)
https://docs.github.com/en/enterprise-cloud@latest/actions/how-tos/reuse-automations/reuse-workflows

[cdce8p]

@sairon Based on my suggestion in the other PR, I added a reusable workflow for the builder. A nice side effect is the added grouping in the workflow run view https://github.com/home-assistant/docker-base/actions/runs/19587880102?pr=328.

Overall the PR should work fine but might still have some rough edges. I wasn't quite sure where the best place to draw the line would be. We can either define most variables in the builder workflow itself and pass it as inputs or do some conditional magic in Set build arguments. For the first attempt I chose a bit of both.

Let me know what you think.

[frenck]

Thanks, @cdce8p 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev

[sairon]

This introduced a bug, the Python images are now tagged incorrectly, as the version suffix is attached to alpine version, while it should be ${{ matrix.python }}-alpine${{ matrix.version }}-${{ github.event.release.tag_name }}. Fix on the way.

[sairon]

Overall the PR should work fine but might still have some rough edges. I wasn't quite sure where the best place to draw the line would be. We can either define most variables in the builder workflow itself and pass it as inputs or do some conditional magic in Set build arguments. For the first attempt I chose a bit of both.

I only looked at the code in detail now, as I didn't pay much attention once it was merged, but after reading it, I think I might prefer to do as much of the conditional magic on the side of the "caller" - currently I had some issues understanding what ends up where (hence the bunch of force-pushed commits above, which included incorrectly staged hunk).

[cdce8p]

This introduced a bug, the Python images are now tagged incorrectly, as the version suffix is attached to alpine version, while it should be ${{ matrix.python }}-alpine${{ matrix.version }}-${{ github.event.release.tag_name }}. Fix on the way.

Thanks for the quick fix!

I only looked at the code in detail now, as I didn't pay much attention once it was merged, but after reading it, I think I might prefer to do as much of the conditional magic on the side of the "caller" - currently I had some issues understanding what ends up where (hence the bunch of force-pushed commits above, which included incorrectly staged hunk).

The added complexity is one of the small downsides unfortunately. Anything left I should help with at this point or would you prefer to do it yourself / leave it as is?