Skip to content

Build, test and push container images #331

Build, test and push container images

Build, test and push container images #331

Triggered via schedule March 14, 2026 23:58
Status Success
Total duration 24m 4s
Artifacts 8

build-and-push.yml

on: schedule
Matrix: Build, test and push
Create multi-platform manifests
15s
Create multi-platform manifests
Update Dockerhub description
0s
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 (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/
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/
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~2L8526.dockerbuild
29 KB
sha256:06ca32de69436a3aeea40ec621ced7b48c4aa271644e613389e294374e0bf710
fedora-python~fedora-python-tox~8TZMFD.dockerbuild
32.3 KB
sha256:d1d037e57a2e63f6d103f5931ba0410a3a07f6baef810eff8c65ce275c0df149
fedora-python~fedora-python-tox~ANDVYH.dockerbuild
29.7 KB
sha256:1ef097a6245dc1ec256a83c5e008172cd464c62e940eb2a1839e639401602a0a
fedora-python~fedora-python-tox~AZ8ME4.dockerbuild
30.1 KB
sha256:165e6e64cb2f61794230a0a7d8d3ac7e8d15034eb8e7e1fcfffe301db99067d5
fedora-python~fedora-python-tox~Q1Y0F8.dockerbuild
33.5 KB
sha256:cf7cb580c56b0e02030f5bf9727252571335fd092a542374db15a16682125e83
fedora-python~fedora-python-tox~QZUSWT.dockerbuild
32.7 KB
sha256:fd285456dde0b8b39f79f1556c218e5765afdefae6e2140ab7ea5a662002f3c0
fedora-python~fedora-python-tox~WYMA1H.dockerbuild
30.8 KB
sha256:874304dd23358af0fd68968af8e665a6737fc6b65ce87f4a9072de9c5518d245
fedora-python~fedora-python-tox~XM0Y1W.dockerbuild
32.8 KB
sha256:2dc580600f45967cf7b87492ce2a4da53cb4b69724c4380361659243295730c9