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

RAC-478 fix : CD workflow 수정 #335

Merged
merged 1 commit into from
Jan 10, 2025
Merged

RAC-478 fix : CD workflow 수정 #335

merged 1 commit into from
Jan 10, 2025

Conversation

ywj9811
Copy link
Member

@ywj9811 ywj9811 commented Jan 10, 2025

🦝 PR 요약

CD workflow 수정

✨ PR 상세 내용

어떤 부분이 어떻게 변경이 되엇나요? - 지우고 작성

🚨 주의 사항

주의할 부분이 무엇인가요? - 지우고 작성

✅ 체크 리스트

  • 리뷰어 설정했나요?
  • Label 설정했나요?
  • 제목 양식 맞췄나요? (ex. RAC-1 feat: 기능 추가)
  • 변경 사항에 대한 테스트 진행했나요?

Summary by CodeRabbit

  • Chores
    • Updated Docker image naming convention in the continuous deployment workflow.
    • Modified Docker build and push commands to use a new repository name.

@ywj9811 ywj9811 self-assigned this Jan 10, 2025
Copy link

coderabbitai bot commented Jan 10, 2025

Walkthrough

The pull request modifies the GitHub Actions workflow file for continuous deployment, specifically changing the Docker image naming convention. The workflow now builds and pushes a Docker image with a new repository name, transitioning from postgraduate_develop to kimseonbae_develop, while maintaining the same latest tag. The core workflow structure and deployment process remain consistent.

Changes

File Change Summary
.github/workflows/CD-develop.yml Updated Docker image build and push commands to use new repository name kimseonbae_develop instead of postgraduate_develop

Poem

🐰 A Docker dance of naming delight,
From postgrad to Kim's project so bright,
One tag, new name, a subtle shift,
Continuous deployment's gentle lift,
Workflows flow with rabbity might! 🚀


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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

Documentation and Community

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/CD-develop.yml (1)

62-63: Consider adding image cleanup and versioning strategy.

A few suggestions to improve the deployment process:

  1. Add cleanup of old postgraduate_develop images to prevent disk space issues
  2. Consider using git SHA or semantic versions instead of just latest tag for better rollback support

Example improvement:

 - name: Build and Push Docker image
   run: |
-    docker build -t ywj9811/kimseonbae_develop:latest .
-    docker push ywj9811/kimseonbae_develop:latest
+    # Build with both version and latest tags
+    docker build -t ywj9811/kimseonbae_develop:${GITHUB_SHA::7} -t ywj9811/kimseonbae_develop:latest .
+    docker push ywj9811/kimseonbae_develop:${GITHUB_SHA::7}
+    docker push ywj9811/kimseonbae_develop:latest
+    
+    # Cleanup old images (optional)
+    docker rmi ywj9811/postgraduate_develop:latest || true
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f93ab1a and f331c45.

📒 Files selected for processing (1)
  • .github/workflows/CD-develop.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: SonarCloud
🔇 Additional comments (1)
.github/workflows/CD-develop.yml (1)

62-63: Verify the existence of docker-compose.kimseonbae.yml on EC2.

The Docker image naming has been updated consistently, but we need to ensure the corresponding compose file exists on the EC2 instance.

Please confirm that /home/ec2-user/config/docker-compose.kimseonbae.yml is properly configured on the EC2 instance before merging.

@ywj9811 ywj9811 merged commit 2cd8f1a into develop Jan 10, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant