-
Notifications
You must be signed in to change notification settings - Fork 66
feat: Migrate TWA test-related workflows #627
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
base: notebooks-v1
Are you sure you want to change the base?
feat: Migrate TWA test-related workflows #627
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
01e48e4
to
a5bfa91
Compare
8b9b78f
to
28f1111
Compare
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.
Really nice investigations/implementations here @yehudit1987 - but for the immediate needs of notebooks-v1
migration - I would prefer we dial back some of these changes to align more with the "status quo" of how kubeflow/kubeflow
implemented these workflows.
2615d17
to
a97625b
Compare
Signed-off-by: Yehudit Kerido <yehudit1987@gmail.com>
a97625b
to
09f01c5
Compare
Migrate frontend tests, multi-arch build, and integration test workflows
Optimize during migration:
• Add npm and Docker build caching for 40-50% faster builds
• Eliminate code duplication by centralizing common library build
• Replace manual multi-arch builds with docker/build-push-action
• Standardize naming conventions and make scripts executable
Resolve issue [TASK] Migrate TWA test-related workflows from kubeflow/kubeflow to notebooks-v1 branch #589