[10.10.2 재배포] Dockerfile 누락 설정변경 추가

[wannabeing]

🔎 작업 내용

• Dockerfile 설정변경이 누락되어 추가

---

🛠️ 변경 사항

• 구현한 주요 로직, 클래스, 메서드 등을 bullet 형식으로 기술해주세요.
• 예)
  • UserService.createUser() 메서드 추가
  • @Email 유효성 검증 적용

---

🧩 트러블 슈팅

• 구현 중 마주한 문제와 해결 방법을 기술해주세요.
• 예)
  • 문제: @Transactional이 적용되지 않음
  • 해결: 메서드 호출 방식 변경 (this. → AopProxyUtils. 사용)

---

🧯 해결해야 할 문제

• 기능은 동작하지만 리팩토링이나 논의가 필요한 부분을 적어주세요.
• 예)D
  • UserController에서 비즈니스 로직 일부 처리 → 서비스로 이전 고려 필요

---

📌 참고 사항

• 기타 공유하고 싶은 정보나 참고한 문서(링크 등)가 있다면 작성해주세요.

---

🙏 코드 리뷰 전 확인 체크리스트

• 불필요한 콘솔 로그, 주석 제거
• 커밋 메시지 컨벤션 준수 (type : )
• 기능 정상 동작 확인

Summary by CodeRabbit

• Refactor
  • Brave 검색 클라이언트 초기화와 도구 검증 로직을 단순화하고 응답 포맷을 정리하여 검색 결과 반환의 일관성을 개선했습니다.
• Tests
  • 빌드 과정에서 테스트 실행을 활성화해 품질을 강화했습니다.
• Chores
  • Brave Search 실행 환경 설치와 경로 설정을 간소화했습니다.
  • 요청 타임아웃을 상향하고 불필요한 자동 설정을 비활성화해 안정성을 높였습니다.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Dockerfile removes MCP toggles, runs tests during build, and switches Brave Search install to a global package. BraveSearchMcpService simplifies initialization and client selection, directly listing tools and returning content as-is. application.properties updates timeouts, stdio command, and Spring AI autoconfiguration flags.

Changes

Cohort / File(s)	Summary
Build & Runtime (Dockerfile) cs25-service/Dockerfile	Removed MCP-related env toggles and Gradle wrapper chmod; build now runs tests (removed -x test). Changed Brave Search install from pinned version to global server-brave-search; removed symlink, chmod, and --help call.
Brave MCP Service Logic cs25-service/src/main/java/com/example/cs25service/domain/ai/service/BraveSearchMcpService.java	Dropped initialization timeout and synchronized init; resolveBraveClient() now directly lists tools and selects client only if brave_web_search exists; simplified error handling; search returns raw content (or empty object) instead of wrapping under results. Removed verbose logging.
Application Configuration cs25-service/src/main/resources/application.properties	Increased MCP timeout 45s→60s; stdio command changed to server-brave-search; added spring.ai.mcp.client.initialized=false; excluded ToolCallingAutoConfiguration.

Sequence Diagram(s)

sequenceDiagram
  participant Service as BraveSearchMcpService
  participant MCP as MCP Client
  participant Tool as Brave Web Tool

  Service->>MCP: listTools()
  MCP-->>Service: tools metadata
  alt brave_web_search present
    Service->>Tool: search(query)
    Tool-->>Service: content (or null)
    Service-->>Service: return content or {}
  else
    Service-->>Service: throw IllegalStateException
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Feat/335 Brave Search(MCP) 도입 #336: 변경된 BraveSearchMcpService 초기화/응답 처리와 직접적으로 겹치는 구현 수정.
• chore: 런타임베이스이미지를 Ubuntu 계열로 변경하여 apt-get 명령어가 동작할 수 있게 변경 #369: Dockerfile의 server-brave-search 설치 방식 변경과 동일 영역 수정.
• 10차 배포 - 7 #368: Dockerfile 및 application.properties의 Brave MCP stdio 설정 변경과 중복.

Suggested reviewers

• HeeMang-Lee
• crocusia
• Kimyoonbeom

Poem

깡충, 토끼는 로그를 줄였지—휙!
도구를 묻고, 있으면 곧장—척!
병렬의 매듭을 가볍게 푼 뒤,
응답은 그대로, 포장지도 없이.
컨테이너 속 바람도 새로워—서버-브레이브, 출발! 🥕✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8ca5e2c and ec70200.

📒 Files selected for processing (3)

• cs25-service/Dockerfile (2 hunks)
• cs25-service/src/main/java/com/example/cs25service/domain/ai/service/BraveSearchMcpService.java (2 hunks)
• cs25-service/src/main/resources/application.properties (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 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.