-
Notifications
You must be signed in to change notification settings - Fork 292
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
Add Helm chart and PR Deployments #9286
Conversation
Warning Rate limit exceeded@kliwniloc has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 5 minutes and 42 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe changes introduce three new GitHub Actions workflows for automating the deployment and cleanup of Kubernetes resources using Helm. The workflows facilitate the deployment of pull requests, the cleanup of resources when pull requests are closed, and the building and pushing of Helm charts. Additional files include a Changes
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 10
🚀 Deployed PR #9286 to https://pr9286.artemis-k8s.ase.cit.tum.de ⏳ It might take up to 10 minutes to fully start up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
Signed-off-by: Colin Wilk <[email protected]>
🚀 Deployed PR #9286 to https://pr9286.artemis-k8s.ase.cit.tum.de ⏳ It might take up to 10 minutes to fully start up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What a nice idea to put the deployments on K8s!
I left you a couple of comments in the GitHub action files and briefly looked over the templates too - they are mostly copied from Matthias though, right?
|
||
on: | ||
pull_request: | ||
types: [opened, synchronize, reopened] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the GH documentation, those 3 values are consistent with the set of default values. I propose to omit them for clarity reasons here
workflow_run: | ||
workflows: ["tests"] | ||
branches: [main] | ||
types: | ||
- completed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this relate to the workflow defined in .github/workflows/test.yml
?
What's the reason for adding a workflow-trigger when your only job is conditional to the action having a pull_request
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need this workflow when the exact same steps are taken on pull_request
anyways?
Please use the PR description template, follow the naming conventions for PR titles and branch names! |
This Pull Request merges the Helm chart from https://github.com/ls1intum/artemis-helm and adds GitHub action workflows to continuously deploy pull requests to Kubernetes.
Summary by CodeRabbit
New Features
Chores
.gitignore
file to exclude unnecessary files from version control.