Skip to content
.github/workflows/publish_api.yml

Set naming conventions for database constraints (#70) #33

Sign in to view logs

Set naming conventions for database constraints (#70)

Set naming conventions for database constraints (#70) #33

Triggered via push December 5, 2023 10:48
@omar-seloomar-selo
pushed f741e4d
main
Status Failure
Total duration 18m 33s
Artifacts –

publish_api.yml

on: push
build-and-push-image
52s
build-and-push-image
build-and-push-charm
17m 26s
build-and-push-charm
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build-and-push-charm
Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
build-and-push-charm
HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"} at /home/runner/work/_actions/canonical/charming-actions/2.4.0/dist/upload-charm/index.js:8603:21 at processTicksAndRejections (node:internal/process/task_queues:96:5)
build-and-push-charm
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/