[SDK] Use new released kfp-server-api package

[Bobgy]

/assign @numerology

We should release a patched kfp shortly after then.
Context: #2977 (comment)
We should change kfp package dependency when releasing a new kfp-server-api package.

---

This change is 

[numerology]

Sorry can you point me to the PR where the server API was changed? Just want to double check if it's backward compatible :)

[Bobgy]

Sorry can you point me to the PR where the server API was changed? Just want to double check if it's backward compatible :)

It's released to pypi directly, code is not checked in here.

[numerology]

Sorry can you point me to the PR where the server API was changed? Just want to double check if it's backward compatible :)

It's released to pypi directly, code is not checked in here.

I see. My understanding is that, because currently in SDK we don't have something like upload_pipeline_version yet, it's okay to declare the backward compatibility. Once we have that, we'll need to bump the lower bound version, right?

Otherwise LGTM

[Bobgy]

@numerology That's a good point, we already have schedule_pipeline method that uses the new no_catchup field: #3201.

We need to increase lower bound version.

[IronPan]

/lgtm

[Ark-kun]

You should probably use kfp-server-api==0.2.5 syntax.

[numerology]

You should probably use kfp-server-api==0.2.5 syntax.

Good catch :) Also make sure there is no space around the '=='

[Bobgy]

Thanks @Ark-kun and @numerology! Does this look good now?

[numerology]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: numerology

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:

• sdk/OWNERS [numerology]

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

[Ark-kun]

Let's resolve the Travis test issues first to avoid upsetting the Prow team.
/hold

[Ark-kun]

@Bobgy Please change requirements.txt accordingly to avoid version conflicts.

[Bobgy]

Sorry I didn't realize it failed, will fix this

[Ark-kun]

Sorry I didn't realize it failed, will fix this

The issue was unexpected. It won't reproduce locally. It seems to be a weird issue in pip triggered by travis: github.com/pypa/pip/issues/6275

/hold cancel
/lgtm

[Bobgy]

Thanks! I thought the error was caused by version inconsistency between requirements.txt and setup.py. Looks like it's not expected.

[Ark-kun]

Thanks! I thought the error was caused by version inconsistency between requirements.txt and setup.py. Looks like it's not expected.

It was a trigger, but usually pip does not stop on those version errors.