-
Notifications
You must be signed in to change notification settings - Fork 699
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 a prow_config.yaml file to configure our prow jobs. #388
Conversation
* See kubeflow/testing#12 * Our prow jobs will trigger a script that will process prow_config.yaml and figure out which workflows to run. * This will allow us to easily run multiple workflows as part of our E2E tests.
/test all |
5 similar comments
/test all |
/test all |
/test all |
/test all |
/test all |
The test failures are due to kubeflow/testing#30 |
@gaocegege @lluunn This is ready for review. The tests are passing; the failure is due to kubeflow/testing#30. |
/test all |
1 similar comment
/test all |
@@ -8,7 +8,7 @@ | |||
// Each object below should correspond to a component in the components/ directory | |||
workflows: { | |||
bucket: "mlkube-testing_temp", | |||
name: "jlewi-tf-k8s-presubmit-test-374-6e32", | |||
name: "some-very-very-very-very-very-long-name-jlewi-tf-k8s-presubmit-test-374-6e32", |
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 we need a very very very long name 🤔
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.
OK, I saw the code below.
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.
LGTM 🎉
/test al |
/test all |
Woo Hoo |
See checkout.sh should support checking out extra repositories. testing#12
Our prow jobs will trigger a script that will process prow_config.yaml
and figure out which workflows to run.
This will allow us to easily run multiple workflows as part of our E2E tests.
Fix one source of flakiness in TFJob test
to fail with a very cryptic error message
This change is