Skip to content

Build, test and push container images #332

Build, test and push container images

Build, test and push container images #332

Triggered via schedule March 21, 2026 23:57
Status Success
Total duration 24m 16s
Artifacts 8

build-and-push.yml

on: schedule
Matrix: Build, test and push
Create multi-platform manifests
19s
Create multi-platform manifests
Update Dockerhub description
Update Dockerhub description
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build, test and push (amd64, py36,py39,py310,py311,py312,py313,py314,py315,py314t,py315t,pypy,pyp...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build, test and push (ppc64le, py39,py311)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build, test and push (arm64, py312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build, test and push (s390x, py39,py310,py312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Create multi-platform manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
fedora-python~fedora-python-tox~5I9X9J.dockerbuild
30.9 KB
sha256:113a603a16f4f7b5b649eb6ef2cc8751a7bd04da8d4722debc20504b2b404131
fedora-python~fedora-python-tox~6V5C7K.dockerbuild
29.3 KB
sha256:23cd862bb97b5697477890249477e160daceda6be70902cc6a6ce8299489a281
fedora-python~fedora-python-tox~HXDDRK.dockerbuild
31.1 KB
sha256:3d7b83bdd2a1c023922975f61cceb5c8a4937ab9735ac4322ab0b22375aedabf
fedora-python~fedora-python-tox~J05I14.dockerbuild
28.8 KB
sha256:54dc2b80b1a0b2e1ac588db9aa0718c4a2f1918818b94439d3e1e02e2a225a84
fedora-python~fedora-python-tox~JZ7XF9.dockerbuild
29.8 KB
sha256:e0d7b0a3238c53045659874420e67b8091ae2e9164a6c5a1817c6bb3d5f91f39
fedora-python~fedora-python-tox~L5LFF9.dockerbuild
31.3 KB
sha256:e1843236cbc58508ed1e09b452989c3a0fdd8e4ccce3a58dc1287efe02cc7603
fedora-python~fedora-python-tox~VN49Q6.dockerbuild
31.1 KB
sha256:ddd961baedd056731f7268c4ec528e548394bd31e022b775959995afd0e66eb7
fedora-python~fedora-python-tox~VWVY9P.dockerbuild
28.8 KB
sha256:218b212f454ae92f7857d564acae5d4db2b5b26dbec38c98729ef47a2f90d4db