Skip to content

Release

Release #21

Re-run triggered November 26, 2024 11:41
Status Failure
Total duration 2m 38s
Artifacts 3

cd.yml

on: workflow_dispatch
Build distribution πŸ“¦
15s
Build distribution πŸ“¦
Publish Docker images 🐳
2m 28s
Publish Docker images 🐳
Create a GitHub release πŸ”–
6s
Create a GitHub release πŸ”–
Publish to PyPI πŸš€
14s
Publish to PyPI πŸš€
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 4 warnings, and 1 notice
Create a GitHub release πŸ”–
Error 422: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
Publish Docker images 🐳
buildx failed with: ERROR: failed to solve: process "/bin/sh -c rye lock --reset --features aws --pyproject viadot/pyproject.toml" did not complete successfully: exit code: 1
The 'as' keyword should match the case of the 'from' keyword: docker/Dockerfile#L73
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: docker/Dockerfile#L95
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: docker/Dockerfile#L140
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L40
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Publish to PyPI πŸš€
Generating and uploading digital attestations

Artifacts

Produced during runtime
Name Size
dyvenia~viadot~TE1MK4.dockerbuild
106 KB
dyvenia~viadot~XTI9H1.dockerbuild
17.6 KB
python-package-distributions
542 KB