"Verify Deployments" timeout policy undocumented

[Thorn1089]

Will this option ever time out if I don't have sufficient availability for the deployment? Or will my build simply run forever unless I configure a timeout separately within my Jenkinsfile? It's unclear from the guides and in-app help text. I stopped a test build after 4 minutes without seeing any indication it would terminate on its own.

[Thorn1089]

Actually it's not clear what the verification option does at all, since I can see my Deployments are successful on GKE yet the Jenkins plugin just keeps spinning endlessly. Please provide documentation on how to use this option or remove it if it is nonfunctional.

[johnlabarge]

There should be a place to add the timeout you desire in the gui. It's been some time since I worked on this and I don't have a local version setup at the moment.

[johnlabarge]

For your other question, verification of a deployment requires that it have the minimum number of available replicas.

[Thorn1089]

Ah, I found the timeout (I also removed the undocumented "VerifyServices" flag I had previously set while I was at it).

I'm now getting this error at the end when my timeout expires:

Failed to verify apps/v1/Deployment: java-db-gke-deploys

java.io.IOException: Failed to launch command args: [kubectl, --kubeconfig, /var/lib/jenkins/workspace/java-web-app_gke-deploys@tmp/.kube4957378958378262705config, config, use-context, gke_andplus-kubernetes_us-east4-a_staging-cluster], status: 1. Logs: error: no context exists with the name: "gke_andplus-kubernetes_us-east4-a_staging-cluster"

However as mentioned, the Deployments and Services are created just fine by the plugin.
Why does it seem unable to then check the status?