Remove the old release-0.16 pre- and post- install jobs.

[Harwayne]

This should fix #3873, but we'll leave that issue open until a release with eventing.yaml has been created.

Proposed Changes

• Remove the old release-0.16 pre- and post- install jobs.

Release Note

NONE

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Harwayne

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• hack/OWNERS [Harwayne]

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

[n3wscott]

you need to push this to the release-0.17 branch, not master

[Harwayne]

you need to push this to the release-0.17 branch, not master

D'oh. Done.

[n3wscott]

/lgtm

[knative-test-reporter-robot]

The following jobs failed:

Test name	Triggers	Retries
pull-knative-eventing-upgrade-tests	2020-08-19 19:33:40.67 +0000 UTC 2020-08-19 19:41:10.861 +0000 UTC 2020-08-19 19:47:10.923 +0000 UTC 2020-08-19 19:54:10.882 +0000 UTC 2020-08-19 20:19:40.658 +0000 UTC	3/3

Job pull-knative-eventing-upgrade-tests expended all 3 retries without success.

[Harwayne]

Discussed in slack. This change is only for release.sh, so it does not affect the code or config. The tests for this PR, and all other PRs in this repo, will fail because it tries to find the latest release's eventing.yaml, which the 0.17.0 release lacks. @lionelvillard agreed that we should just force this in.

[knative-prow-robot]

@Harwayne: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-knative-eventing-upgrade-tests	1aa3077	link	/test pull-knative-eventing-upgrade-tests
pull-knative-eventing-conformance-tests	1aa3077	link	/test pull-knative-eventing-conformance-tests

Full PR test history. Your PR dashboard.

Details

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.