Skip to content

fix(kubernetes): non-string annotation values cause the annotation map in a manifest's Go representation to be empty #25

fix(kubernetes): non-string annotation values cause the annotation map in a manifest's Go representation to be empty

fix(kubernetes): non-string annotation values cause the annotation map in a manifest's Go representation to be empty #25

Triggered via pull request January 10, 2024 17:11
Status Success
Total duration 1m 25s
Artifacts 1

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Cannot open: File exists
build
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
build
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Artifacts

Produced during runtime
Name Size
build Expired
51.7 MB