Fixing the GO import paths to reference the kubeflow/pipelines repository #24
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@vicaire: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
…row jobs. (kubeflow#25) Currently each repository needs to build a new Docker container. The sole purpose of this container is to specify the path to the Argo workflow to run. We can simplify this by just allowing each repository to define a "prow_config.yaml" file at the root of the repository and then having a single binary which will read that config file and use it to figure out which workflows to invoke This fixes kubeflow#24 We also add support for running multiple workflows. This will make it easy to start using prow to build our containers on each commit (kubeflow#19)
Signed-off-by: Ce Gao <gaoce@caicloud.io>
Add unit test wf
This change is