Component releasing for 0.1.17

[gaoning777]

release new components and remove the resnet image release in the release script

---

This change is 

[gaoning777]

/retest

[gaoning777]

/test kubeflow-pipeline-e2e-test

[gaoning777]

/test kubeflow-pipeline-e2e-test

[Ark-kun]

Can you also try replacing the component branch in samples from master to 439d90cf194cade07b2a6ede3f7a493b08b537e9 ?

[gaoning777]

/test kubeflow-pipeline-e2e-test

[gaoning777]

Can you also try replacing the component branch in samples from master to 439d90cf194cade07b2a6ede3f7a493b08b537e9 ?

Which files exactly? you mean which components in the sample directory?

[Ark-kun]

I meant

pipelines/samples/kubeflow-tf/kubeflow-training-classification.py

Line 21 in d24dba5

dataflow_tf_transform_op = components.load_component_from_url('https://raw.githubusercontent.com/kubeflow/pipelines/master/components/dataflow/tft/component.yaml')

and

pipelines/samples/xgboost-spark/xgboost-training-cm.py

Line 22 in d24dba5

confusion_matrix_op = components.load_component_from_url('https://raw.githubusercontent.com/kubeflow/pipelines/master/components/local/confusion_matrix/component.yaml')

I should probably extend the release.sh script to do that automatically.

[Ark-kun]

Note that the SHA you use when loading components is different than the image SHA. (It's actually the SHA of your commit where you change the image tags.)

[gaoning777]

Then it requires two commit, then?

[Ark-kun]

Then it requires two commit, then?

Yes. But they can be submitted in one PR.
I'll be changing the release.sh script to do that automatically in future.

[gaoning777]

that is not a good a idea to reference a yaml that exists in other forks

[gaoning777]

/test kubeflow-pipeline-sample-test

[IronPan]

Here are the recommended steps:

1. Update the images tag in component folder to latest version that tests pass, using release script and run against component/ dir.
2. Merge the PR in step 1 and wait for test pass
3. Update the image tag in sample folders to merge SHA in step 2, using release script and run against sample/ dir.
4. Merge the PR in step 3.

Later when we deprecate the intermediate YAML the regular process will resume.

[gaoning777]

SGTM

[IronPan]

do you want to revert the changes in the sample directory? I think it's fine to change samples too but it will be a overriden in the next PR.

[IronPan]

/lgtm

[gaoning777]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gaoning777

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:

• components/OWNERS [gaoning777]
• samples/OWNERS [gaoning777]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Ark-kun]

1. Update the images tag in component folder to latest version that tests pass, using release script and run against component/ dir.
2. Merge the PR in step 1 and wait for test pass
3. Update the image tag in sample folders to merge SHA in step 2, using release script and run against sample/ dir.

@IronPan
There is no problem in updating all images in both components directory and samples directory at the same time. The release script is doing the right thing.
There is no need to split this step in two/three.