Disable service binding related integration tests

[feloy]

What type of PR is this:

/area testing

The purpose of this PR is to test the impact of removing the integration tests related to service binding.

It introduces an SKIP_SERVICE_BINDING_TESTS environment variable which indidate to skip tests related to service binding.

This variable has been set to true for Kubernetes, OpenShift and Windows tests on IBM Cloud, to disable these tests for PRs.

The tests will still run during the nightly tests.

[netlify]

✅ Deploy Preview for odo-docusaurus-preview canceled.

Name	Link
🔨 Latest commit	2f4f886
🔍 Latest deploy log	https://app.netlify.com/sites/odo-docusaurus-preview/deploys/6495a416c434350009817f59

[odo-robot]

OpenShift Unauthenticated Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

NoCluster Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

Validate Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

Windows Tests (OCP) on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Docs Tests on commit d9d868f finished with errors.
View logs: TXT HTML

[odo-robot]

OpenShift Tests on commit bf0b4ed finished successfully.
View logs: TXT HTML

[valaparthvi]

e2e_test.go:Context("starting with non-empty Directory add Binding", func() {
can use skipping.

Also, wouldn't you need to modify IBM pipelines to export the env var? I believe the tests are still run on OpenShift, since I do not see any difference between the number of k8s and oc tests.

[feloy]

e2e_test.go:Context("starting with non-empty Directory add Binding", func() { can use skipping.

No, I would like to keep the tests for e2e tests.

[valaparthvi]

Also, wouldn't you need to modify IBM pipelines to export the env var? I believe the tests are still run on OpenShift, since I do not see any difference between the number of k8s and oc tests.

In case you missed.

[feloy]

Also, wouldn't you need to modify IBM pipelines to export the env var? I believe the tests are still run on OpenShift, since I do not see any difference between the number of k8s and oc tests.

In case you missed.

I defined the env var in the pipelines, but after the job has been created. It seems the env variables are considered at the time the job is created (not the time it is started).

Let me try again

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[feloy]

/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

[FAILED] [74.869 seconds]
User guides: Quickstart test Java quickstart guide [It] should test the complete java springboot quickstart output in order
/go/odo_1/tests/documentation/user-guides/doc_user_guides_quickstart_test.go:217

  [odo]  âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

[openshift-ci]

@feloy: Overrode contexts on behalf of feloy: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

In response to this:

/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests

[FAILED] [74.869 seconds]
User guides: Quickstart test Java quickstart guide [It] should test the complete java springboot quickstart output in order
/go/odo_1/tests/documentation/user-guides/doc_user_guides_quickstart_test.go:217

 [odo]  âš   0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

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.