Skip to content

[PR] Post 상세 조회 시 발생하는 DTO 에러 해결 #92

[PR] Post 상세 조회 시 발생하는 DTO 에러 해결

[PR] Post 상세 조회 시 발생하는 DTO 에러 해결 #92

Triggered via pull request October 11, 2023 09:03
Status Failure
Total duration 2m 45s
Artifacts

dev-build.yml

on: pull_request
Build Dockerized Development
2m 14s
Build Dockerized Development
Kubernetes resource update
11s
Kubernetes resource update
Fit to window
Zoom out
Zoom in

Annotations

1 error and 13 warnings
Kubernetes resource update
Process completed with exit code ***.
Build Dockerized Development
The following actions uses node***2 which is deprecated and will be forced to run on node***6: actions/cache@v2, docker/setup-buildx-action@79abd3f86f79a9d68a23c75a09a9a8***89262adf, hmanzur/actions-set-secret@v2.0.0. For more info: https://github.blog/changelog/2023-06-***3-github-actions-all-actions-will-run-on-node***6-instead-of-node***2-by-default/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Build Dockerized Development
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
Kubernetes resource update
The following actions uses node***2 which is deprecated and will be forced to run on node***6: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-***3-github-actions-all-actions-will-run-on-node***6-instead-of-node***2-by-default/