pipeline_jenkins_e2e.go CI sanity check

[gabemontero]

temp commit to make sure e2e-aws-jenkins fires automatically, and that it runs to completion after our recent CI fixing efforts

[gabemontero]

/hold

[gabemontero]

ok e2e-aws-jenkins launched ... so (re)verified that openshift/release change worked

[gabemontero]

my test describe change of course needed a bindata update :-(

we'll wait for the e2e-aws-jenkins result before deciding whether I need to worry about that for this litmus test

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gabemontero
To complete the pull request process, please assign smarterclayton after the PR has been reviewed.
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.

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

Needs approval from an approver in each of these files:

• test/extended/builds/OWNERS [gabemontero]
• test/extended/util/annotate/OWNERS

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

[openshift-ci]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-gcp-builds	afa2e29	link	/test e2e-gcp-builds
ci/prow/e2e-aws-serial	afa2e29	link	/test e2e-aws-serial
ci/prow/e2e-metal-ipi-ovn-ipv6	afa2e29	link	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-gcp	f446001	link	/test e2e-gcp
ci/prow/e2e-gcp-upgrade	f446001	link	/test e2e-gcp-upgrade

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.