deploy 또 또 변경

[roode1017]

Summary by CodeRabbit

• Chores
  • CI/CD 워크플로우를 업데이트하여 EC2에서 직접 빌드·배포하도록 변경했습니다.
  • 배포 시 필요한 프로젝트 소스와 환경변수 파일(.env)만 업로드하도록 조정했습니다.
  • EC2에서 Docker 및 docker-compose 플러그인 검증/설치를 자동화하고, 서비스 중지·재빌드·재기동 절차를 정비했습니다.
  • CloudFront 무효화 단계의 순서를 재정렬해 배포 흐름을 간소화했습니다.
  • 단계 명칭과 설명을 개선해 배포 과정의 가독성을 높였습니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

CI 배포 워크플로에서 로컬 JDK/Gradle 빌드와 JAR/Dockerfile 업로드를 제거하고, 프로젝트 소스 및 .env를 EC2로 업로드한 뒤 EC2에서 docker-compose로 빌드/배포하도록 변경. Docker 및 compose-plugin 설치/검증 로직 추가. CloudFront 무효화 단계 번호 조정.

Changes

Cohort / File(s)	Summary of Changes
CI/CD Workflow .github/workflows/deploy.yml	로컬 Java/Gradle 빌드 제거. 업로드 대상을 backendProject/**, docker-compose-prod.yml, .env로 변경(빌드 산출물 및 Dockerfile 제외). EC2 배포 스크립트에서 원격 .env 생성 제거 및 Docker/compose 설치 검증 추가. docker compose로 stop/build(no-cache)/up 수행. CloudFront 무효화 단계 라벨/순서 조정. 단계명/주석 정리.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as GitHub Actions
  participant EC2 as EC2 Host
  participant Docker as Docker Engine
  participant CF as CloudFront

  Dev->>EC2: SCP 업로드 (backendProject/**, docker-compose-prod.yml, .env)
  Dev->>EC2: SSH 접속 후 배포 스크립트 실행
  EC2->>EC2: docker/compose-plugin 존재 확인 및 필요시 설치
  EC2->>Docker: docker daemon enable/start, 권한 설정
  EC2->>Docker: docker compose -f docker-compose-prod.yml down
  EC2->>Docker: docker compose -f docker-compose-prod.yml build --no-cache
  EC2->>Docker: docker compose -f docker-compose-prod.yml up -d
  Note over EC2,Docker: (선택) 이미지 정리 docker image prune -f
  Dev->>CF: CloudFront 무효화 요청
  CF-->>Dev: 무효화 진행 응답

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Feat/#76 prod 관련 파일들 수정 #77 — 동일 워크플로우 파일 수정으로 업로드 대상과 .env 처리 방식이 상충(이 PR은 .env 업로드, 상대 PR은 원격 생성).
• 배포를 위한 docker-compose 파일 추가 및 securityConfig 수정, deploy 파일 추가 #61 — 같은 deploy.yml에서 로컬 빌드 제거와 업로드 아티팩트 전환 등 유사 변경을 수행.

Suggested labels

enhancement

Poem

밤하늘 깡충, 토끼는 말해요 🐇
“이젠 EC2에서 끓여봐요, 따끈한 배포 스튜!”
자바 냄비는 치우고, 도커 주전자 휘익—
compose 한 잔 따르면 서비스가 딱딱!
바람처럼 무효화, 구름길 CF도 싹 ☁️

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b75f459 and 1b406b6.

📒 Files selected for processing (1)

• .github/workflows/deploy.yml (3 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.