Build and publish teemtee images via github action

[lukaszachy]

I've put it as a separate action triggered manually because I'm out of ideas how to trigger this automatically during the release process. Containers use copr @teemtee/stable to get the builds, and those have to exists at the time we are building the images.

Any ideas?

Pull Request Checklist

• implement the feature
• write the documentation

[lukaszachy]

I've tried in my fork for 'mini' (and my repo) and it seems to work https://github.com/lukaszachy/tmt/actions/runs/13834189789/job/38705231266

[lukaszachy]

Currently we do

tmt/docs/contribute.rst

Line 733 in 0157aea

* Once the non development `copr build`__ is completed, move the

With this PR that bullet will change to ~ Once non development [copr build](https://copr.fedorainfracloud.org/coprs/g/teemtee/stable/builds/) is completed trigger the <LINK THIS ACTION>

But ideally this action will be just mentioned in Handle manually what did not went well:

[martinhoyer]

latest is already default. Just FTR, not saying it's wrong to have it here explicitly.

[lukaszachy]

right you are, i'll drop it

[martinhoyer]

I was looking into the build&publish best practices and found nothing useful. The redhat-actions build and push actions seems to be not updated since about a year ago. Are people using tekton/konflux?

One idea - would using github image registry and "registry sync" action make sense?

[martinhoyer]

fwiw, I've been playing with the tmt images - bf73279 (#3605) Not exactly related, but maybe a little :)

[lukaszachy]

Are people using tekton/konflux?

That would be good for dogfooding purposes, but I don't think it is worth the setup hassle right now.

[martinhoyer]

Containers use copr @teemtee/stable to get the builds, and those have to exists at the time we are building the images.

Any ideas?

For now, I'd trigger them manually once the updates are in the Fedora repos and use those instead od copr. Also would be good to build aarch64.