패키지 캐싱을 적용했더니 AWS Amplify에서 배포가 실패합니다.

Question

안녕하세요. Azure DevOps에서 CI를 돌리고, 성공 시 AWS CodeCommit을 통해 AWS Amplify로 배포를 하고 있는 상태입니다. 최근에 CI 시간을 줄이고자 패키지 캐싱을 도입을 했습니다. 헌데 그 과정에서 CI가 성공하고 머지되어 Amplify에서 배포를 하는 과정에서 실패합니다.Azure DevOps 파이프라인입니다.trigger: - master - develop pool: vmImage: 'ubuntu-latest' variables: - group: aws-access-for-pipeline - name: AWS_USERNAME value: '$(AWS_GIT_USERNAME)' - name: AWS_PASSWORD value: '$(AWS_GIT_PASSWORD)' - name: YARN_CACHE_FOLDER value: $(Pipeline.Workspace)/.yarn steps: - task: NodeTool&#64;0 displayName: Node Install inputs: versionSpec: '16.x' - task: Cache&#64;2 inputs: key: '&#34;yarn&#34; | &#34;$(Agent.OS)&#34; | yarn.lock' restoreKeys: | &#34;yarn&#34; | &#34;$(Agent.OS)&#34; &#34;yarn&#34; path: $(YARN_CACHE_FOLDER) displayName: Cache Yarn packages - script: yarn --frozen-lockfile displayName: 'Install Dependencies' - script: yarn build:dev displayName: 'Build' - script: | sudo apt-get install gridsite-clients git clone --mirror https://${AZURE_GIT_USERNAME}:$(urlencode ${AZURE_GIT_PASSWORD})&#64;${AZURE_REPO_URL} repo-mirror cd repo-mirror git push --mirror https://${AWS_GIT_USERNAME}:$(urlencode ${AWS_GIT_PASSWORD})&#64;${AWS_REPO_URL} displayName: 'Sync repository with AWS CodeCommit' env: AZURE_REPO_URL: $(AZURE_REPO_URL) AZURE_GIT_USERNAME: $(AZURE_GIT_USERNAME) AZURE_GIT_PASSWORD: $(AZURE_GIT_PASSWORD) AWS_REPO_URL: $(AWS_REPO_URL) AWS_GIT_PASSWORD: $(AWS_PASSWORD) AWS_GIT_USERNAME: $(AWS_USERNAME)아래는 amplify.yml입니다. prebuild.sh는 센트리 관련 세팅이라 큰 의미는 없습니다.version: 1 env: variables: SENTRY_AUTH_TOKEN: ~~~ frontend: phases: preBuild: commands: - yarn install --frozen-lockfile - sh amplify-scripts/prebuild.sh build: commands: - yarn build:$BUILD_ENV artifacts: baseDirectory: .next files: - '**/*' cache: paths: - node_modules/**/* - .next/cache이때 Amplify 배포 과정에서 다음과 같은 에러가 발생합니다.2023-06-28T04:51:41.059Z [INFO]: ➤ YN0000: ┌ Post-resolution validation ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden. 2023-06-28T04:51:41.064Z [INFO]: ➤ YN0000: └ Completed ➤ YN0000: Failed with errors in 3s 173ms 2023-06-28T04:51:41.092Z [ERROR]: !!! Build failed 2023-06-28T04:51:41.092Z [INFO]: Please check the supported SSR features to find if your build failure is related to an unsupported feature: https://docs.aws.amazon.com/amplify/latest/userguide/ssr-Amplify-support.html#supported-unsupported-features. You may also find this troubleshooting guide useful: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-ssr-deployment.html 2023-06-28T04:51:41.092Z [ERROR]: !!! Non-Zero Exit Code detected 2023-06-28T04:51:41.092Z [INFO]: # Starting environment caching... 2023-06-28T04:51:41.093Z [INFO]: # Uploading environment cache artifact... 2023-06-28T04:51:41.154Z [INFO]: # Uploaded environment cache artifact 2023-06-28T04:51:41.154Z [INFO]: # Environment caching completed Terminating logging... ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.이 부분이 문제인데요, 아무래도 yarn.lock을 배포 과정에서 수정하려는 시도로 포착하여 실패시키는 것 같습니다. 해결 방법이 어찌 될까요..? 참고로 Next.js 프로젝트이며 버전은 13.2.1입니다. yarn install --frozen-lockfile을 해도, yarn install을 해도 결과는 똑같았습니다. 구글링을 좀 한 결과 commands: - YARN_ENABLE_IMMUTABLE_INSTALLS&#61;false yarn install해당 커맨드로 진행을 해봤는데, 이 경우에는 다른 에러가 발생합니다.2023-06-28T07:49:57.592Z [INFO]: # Executing command: yarn build:$BUILD_ENV 2023-06-28T07:49:58.590Z [INFO]: info - Loaded env from /codebuild/output/src183901612/src/tf-monorepo/.env.local 2023-06-28T07:49:58.681Z [WARNING]: error - Failed to load next.config.js, see more info here https://nextjs.org/docs/messages/next-config-error 2023-06-28T07:49:58.687Z [WARNING]: 2023-06-28T07:49:58.687Z [WARNING]: > Build error occurred 2023-06-28T07:49:58.689Z [WARNING]: Error: Cannot find module 'esbuild-loader'해당 PR을 머지할 때 esbuild-loader를 설치하여 진행했는데, 이걸 찾지를 못하는 것 같습니다..고견을 구합니다. 감사합니다.

패키지 캐싱을 적용했더니 AWS Amplify에서 배포가 실패합니다.

0개의 답변

#amplify 목록