Skip to content

[docs]: 포트폴리오 PDF 업데이트 (#422) #107

[docs]: 포트폴리오 PDF 업데이트 (#422)

[docs]: 포트폴리오 PDF 업데이트 (#422) #107

Triggered via push March 10, 2026 16:04
Status Failure
Total duration 8m 24s
Artifacts

dev.yml

on: push
환경 변수 설정
3s
환경 변수 설정
CI_CHECK(spotless, sonar) 정적분석  /  spotless-sonar
1m 51s
CI_CHECK(spotless, sonar) 정적분석 / spotless-sonar
Matrix: 서비스 빌드 / build
서비스 배포  /  서비스 배포하기
6m 29s
서비스 배포 / 서비스 배포하기
Fit to window
Zoom out
Zoom in

Annotations

1 error and 8 warnings
CI_CHECK(spotless, sonar) 정적분석 / spotless-sonar
Process completed with exit code 1.
환경 변수 설정
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
환경 변수 설정
Skip output 'image-name' since it may contain secret.
서비스 빌드 / build (17)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v3, docker/login-action@v3, gradle/gradle-build-action@v2. 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 (17)
Failed to restore v8-gradle|Linux|배포 워크플로우-build[4c861f6be0267530d1eeea356b3952a2]-a7131321e8d08838b27bf709097350554016a401: Error: Cache service responded with 400
서비스 빌드 / build (17)
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-10-11-github-actions-deprecating-save-state-and-set-output-commands/
CI_CHECK(spotless, sonar) 정적분석 / spotless-sonar
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v3, gradle/gradle-build-action@v2. 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/
CI_CHECK(spotless, sonar) 정적분석 / spotless-sonar
Failed to restore v8-gradle|Linux|배포 워크플로우-spotless-sonar[37a6259cc0c1dae299a7866489dff0bd]-a7131321e8d08838b27bf709097350554016a401: Error: Cache service responded with 400
서비스 배포 / 서비스 배포하기
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/