[GMSS-104] CD 파이프라인 설정 - #20
Merged
Merged
Conversation
seunghee17
marked this pull request as draft
August 7, 2026 14:17
seunghee17
marked this pull request as ready for review
August 7, 2026 14:27
soyeonLee126
reviewed
Aug 8, 2026
soyeonLee126
approved these changes
Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
작업 개요
fastlane + GitHub Actions 기반 CD 파이프라인을 구축한다. push된 release APK를 Firebase App Distribution(inner-tester)에 자동 배포하고, 빌드 실패를 유발하던
local.properties미작성 문제를 수정한다.작업 유형
변경 사항
distributelane 정의 —:app:assembleRelease빌드 후 Firebase App Distribution 업로드.github/workflows/cd.yml추가 — google-services.json / 서명 키스토어 / Firebase 서비스 계정 키를 시크릿에서 복원해 CI 빌드·서명·배포 수행%h %s)permissions: contents: write→read로 최소권한 조정 (태그 push 로직 제거에 따라 불필요)mainpush로 제한100000 + GITHUB_RUN_NUMBER로 주입, versionName은app/build.gradle.kts에 고정값(0.1.0) 유지관련 이슈
관련 작업 (Notion)
스크린샷 / 동작 화면
체크리스트
develop으로 설정되어 있다feat:,fix:등)을 따른다리뷰 요청 사항
mainpush로 제한한 것이 배포 전략(언제 실제 배포가 나가야 하는지)과 맞는지 확인 부탁드립니다FIREBASE_TESTER_GROUPS(inner-tester)가 워크플로우에 하드코딩되어 있는데 이대로 유지할지 확인 부탁드립니다 만약 유지한다면 테스트앱을 받고자 하는 사용자inner-tester에서 초대 부탁드립니다!