-
Notifications
You must be signed in to change notification settings - Fork 82
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
[CI/CD] Automatically build the router docker image via github action #74
Comments
Do we have the end-to-end test for router now? |
We have a functionality test for the whole helm chart, but not specifically for router. |
Hi @ApostaC, I’d really like to help out with this task. Let me know if I can take it on! |
- Add router-e2e-test workflow for PR validation with performance tests - Add router-docker-release workflow for automated image builds
- Add router-e2e-test workflow for PR validation with performance tests - Add router-docker-release workflow for automated image builds Signed-off-by: Sozhan Natarajan <[email protected]>
…oject#74) - Enhance path handling in minikube and router scripts - Update workflow configurations for better reliability - Fix Python dependencies and test requirements - Improve test environment setup and execution Signed-off-by: Sozhan Natarajan <[email protected]>
* feat(ci): add GitHub Actions workflows for router (#74) - Add router-e2e-test workflow for PR validation with performance tests - Add router-docker-release workflow for automated image builds - Enhance path handling in minikube and router scripts - Update workflow configurations for better reliability - Fix Python dependencies and test requirements - Improve test environment setup and execution Signed-off-by: Sozhan Natarajan <[email protected]>
Right now, we don't have an automatic pipeline to build the docker image for the router.
Ideally, every time there is merged a PR about the router, there should be a GitHub action to automatically build the docker image and release it.
Also, when PR is created and ready to merge (not merged yet), there should be a way to trigger the end-to-end test pipeline to test the router.
The text was updated successfully, but these errors were encountered: