Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat : main, dev PR시 CI 구현 #158

Merged
merged 10 commits into from
Jan 7, 2025
Merged

feat : main, dev PR시 CI 구현 #158

merged 10 commits into from
Jan 7, 2025

Conversation

sunghyun0610
Copy link
Collaborator

@sunghyun0610 sunghyun0610 commented Jan 6, 2025

📌 관련 이슈


#157

💭 작업 내용


main, dev 브랜치 PR시 CI 구현

  1. PR시 트리거로 작동
  2. 자동화 빌드 검증
  3. 테스트는 생략 -> 저희가 테스트코드를 잘 안짜기 때문

🤔 참고 사항


테스트에 대한 검증은 일단 생략되었습니다.

📸 스크린샷(선택)


💬 리뷰 요구사항(선택)

테스트코드 검증을 포함시킬까요?
snoarqube를 통해 코드 분석 과정을 포함시킬까요?

@sunghyun0610 sunghyun0610 self-assigned this Jan 6, 2025
@sunghyun0610 sunghyun0610 added the ✨ Feature 기능 개발 label Jan 6, 2025
Copy link
Collaborator

@macmorning0116 macmorning0116 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니다!

name: CI Pipeline

on:
pull_request:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

혹시 push가 아닌 pr로 하신 이유가 있으실까요?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

이 코드는 CI (빌드->테스트 )까지만 자동화하는거라 main에대해 PR을 날리면 push되기전에 검증하는 로직입니다.
검증 이후 저희 승인을 하고 머지가되면 push가되고 그후에 CD에대한 코드가 작동하고 배포가 되는 flow로 생각하였습니다

with:
fetch-depth: 0

- name: List project files
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

굳이 하는 이유가 있나요?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

아 이건 디버깅과정에서 gradlew위치를 확인하기 위해 필요했었습니다!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

여기서

# Configure Gradle for optimal use in GitHub Actions, including caching of downloaded dependencies.
# See: https://github.com/gradle/actions/blob/main/setup-gradle/README.md
- name: Setup Gradle
uses: gradle/actions/setup-gradle@af1da67850ed9a4cedd57bfd976089dd991e2582 # v4.0.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

어떤 용도인가요??

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gradle 버전관리와 캐시활용해서 이미 다운로드해 둔 의존성(라이브러리)들을 재사용하여, 매번 의존성을 다시 받지 않도록 빌드 속도를 높이는 효과가 있다합니다!

@sunghyun0610 sunghyun0610 merged commit 81e2e3d into main Jan 7, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ Feature 기능 개발
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants