-
Notifications
You must be signed in to change notification settings - Fork 2
176 lines (149 loc) · 6.46 KB
/
rankit-multiaz-cicd.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
name: rankit-multiaz-rolling-zerodowntime-cicd
on:
push:
branches: [ "develop" ]
jobs:
build:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- uses: actions/checkout@v4
# 1. JDK 17 설정
- name: Set up JDK 17
uses: actions/setup-java@v4
with:
java-version: '17'
distribution: 'temurin'
# 2. Gradle 설정
- name: Setup Gradle
uses: gradle/actions/setup-gradle@417ae3ccd767c252f5661f1ace9f835f9654f2b5 # v3.1.0
# 3. Jar 파일 빌드 (테스트 제외)
- name: Build with Gradle Wrapper
run: ./gradlew -x test bootJar
# 4. Docker Buildx 설정
- name: Set up Docker Build
uses: docker/setup-buildx-action@v1
# 5. Docker 로그인
- name: Login to Docker Hub
uses: docker/login-action@v1
with:
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_TOKEN }}
# 6. Docker 이미지 빌드 및 푸시
- name: Build and push Docker image
run: |
docker build -t ${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest .
docker push ${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest
deploy:
runs-on: ubuntu-latest
needs: build
permissions:
contents: read
steps:
# 1. AWS CLI 설치
- name: Install AWS CLI
run: |
sudo apt-get update
sudo apt-get install awscli -y
# 2. AWS 자격 증명 설정
- name: Configure AWS credentials
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
run: |
aws configure set aws_access_key_id $AWS_ACCESS_KEY_ID
aws configure set aws_secret_access_key $AWS_SECRET_ACCESS_KEY
aws configure set region ap-northeast-2 # 서울 AWS 리전을 설정
# 3. EC2 인스턴스 대상 등록 해제 (EC2-A)
- name: Deregister EC2-A from Target Group
run: |
aws elbv2 deregister-targets \
--target-group-arn ${{ secrets.TARGET_GROUP_ARN }} \
--targets Id=${{ secrets.EC2_A_ID }}
# 4. EC2-A에 Docker 컨테이너 배포
- name: Deploy to EC2-A via SSM
run: |
aws ssm send-command \
--instance-ids "${{ secrets.EC2_A_ID }}" \
--document-name "AWS-RunShellScript" \
--parameters 'commands=[
"if [ $(docker ps -q -f \"ancestor=${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest\" -f \"status=running\") ]; then docker stop $(docker ps -q -f \"ancestor=${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest\"); fi",
"docker pull ${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest",
"docker-compose -f docker-compose.yml up -d",
"sleep 10",
"docker-compose -f docker-compose.yml logs"
]' \
--comment "Deploying application to EC2-A"
# 5. EC2-A에서 헬스체크 수행
- name: Perform health check on EC2-A
id: healthcheck-ec2-a
run: |
RESULT=$(aws ssm send-command \
--instance-ids "${{ secrets.EC2_A_ID }}" \
--document-name "AWS-RunShellScript" \
--parameters 'commands=[
"curl -f http://localhost:8080/ || echo \"Health check failed on EC2-A\""
]' \
--comment "Performing health check on EC2-A" \
--query "Command.CommandId" \
--output text)
sleep 10 # 헬스 체크 결과를 기다리기 위해 대기
OUTPUT=$(aws ssm list-command-invocations --command-id $RESULT --details --output json)
# 헬스 체크 실패 여부 확인
if echo "$OUTPUT" | grep -q "Health check failed"; then
echo "Health check failed on EC2-A"
exit 1 # 파이프라인 종료
fi
# 6. EC2 인스턴스 대상 재등록 (EC2-A)
- name: Register EC2-A to Target Group
run: |
aws elbv2 register-targets \
--target-group-arn ${{ secrets.TARGET_GROUP_ARN }} \
--targets Id=${{ secrets.EC2_A_ID }}
# 7. EC2 인스턴스 대상 등록 해제 (EC2-C)
- name: Deregister EC-C from Target Group
run: |
aws elbv2 deregister-targets \
--target-group-arn ${{ secrets.TARGET_GROUP_ARN }} \
--targets Id=${{ secrets.EC2_C_ID }}
# 8. EC2-C에 Docker 컨테이너 배포
- name: Deploy to EC2-C via SSM
run: |
aws ssm send-command \
--instance-ids "${{ secrets.EC2_C_ID }}" \
--document-name "AWS-RunShellScript" \
--parameters 'commands=[
"if [ $(docker ps -q -f \"ancestor=${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest\" -f \"status=running\") ]; then docker stop $(docker ps -q -f \"ancestor=${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest\"); fi",
"docker pull ${{ secrets.DOCKER_USERNAME }}/rankitrun-be:latest",
"docker-compose -f docker-compose.yml up -d",
"sleep 15", # 컨테이너가 시작될 시간을 기다립니다.
"docker-compose -f docker-compose.yml logs"
]' \
--comment "Deploying application to EC2-C"
# 9. EC2-C에서 헬스체크 수행
- name: Perform health check on EC2-C
id: healthcheck-ec2-c
run: |
RESULT=$(aws ssm send-command \
--instance-ids "${{ secrets.EC2_C_ID }}" \
--document-name "AWS-RunShellScript" \
--parameters 'commands=[
"curl -f http://localhost:8080/ || echo \"Health check failed on EC-C\""
]' \
--comment "Performing health check on EC-C" \
--query "Command.CommandId" \
--output text)
sleep 10 # 헬스 체크 결과를 기다리기 위해 대기
OUTPUT=$(aws ssm list-command-invocations --command-id $RESULT --details --output json)
# 헬스 체크 실패 여부 확인
if echo "$OUTPUT" | grep -q "Health check failed"; then
echo "Health check failed on EC-C"
exit 1 # 파이프라인 종료
fi
# 10. EC2 인스턴스 대상 재등록 (EC2-C)
- name: Register EC-C to Target Group
run: |
aws elbv2 register-targets \
--target-group-arn ${{ secrets.TARGET_GROUP_ARN }} \
--targets Id=${{ secrets.EC2_C_ID }}