Revision 31d2e10bf0b053fbe7905065d951548ad18eabcc authored by Jeremy Lewi on 21 September 2018, 09:17:41 UTC, committed by k8s-ci-robot on 21 September 2018, 09:17:41 UTC
* Related to #141 katib releaser * Related to kubeflow/kubeflow#1574 use prow to build our images * We are moving to using prow to run our release workflows and treating them just like regular workflows. * We are doing this because we need to get regular signal about whether the image builds are succeeding by running on postsubmit. * We also want to run them on presubmit so that we can verify any changes to the workflwo don't break the workflow. * Rather than define a new workflow to build the images; we can just reuse the existing E2E workflow which already builds all the images. We just change postsubmit to push to kubeflow-images-public. * Delete the releaser app; we will just the existing E2E test workflow and have that push to gcr.io/kubeflow-images-public on postsubmit.
1 parent 81f2b74
| File | Mode | Size |
|---|---|---|
| MinikubeDemo | ||
| MinikubeDemo.md | -rw-r--r-- | 11.0 KB |
| gpu-example.yaml | -rw-r--r-- | 835 bytes |
| grid-example.yaml | -rw-r--r-- | 953 bytes |
| hypb-example.yaml | -rw-r--r-- | 1.1 KB |
| random-example.yaml | -rw-r--r-- | 1.5 KB |
| workerConfigMap.yaml | -rw-r--r-- | 1.3 KB |
Computing file changes ...
