Bug 1401453

Summary:	It is better to disable 'Start Pipeline/Build' button for pipeline when jenkins pod is not ready yet
Product:	OpenShift Container Platform	Reporter:	Xingxing Xia <xxia>
Component:	Management Console	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED NOTABUG	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.4.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-05 16:09:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Xingxing Xia 2016-12-05 10:13:57 UTC

Description of problem:
It is better to disable 'Start Pipeline/Build' button for pipeline when jenkins pod is not ready yet. Otherwise, user may click 'Start Pipeline/Build' button in advance before it is ready to start a pipeline build, which may cause pipeline build exception such as https://bugzilla.redhat.com/show_bug.cgi?id=1366223 (addressed. Listed just as example of 'exception') or whatever.

Version-Release number of selected component (if applicable):
openshift v3.4.0.32

How reproducible:
Always

Steps to Reproduce:
1. Create a jenkinsPipelineStrategy bc
$ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json

2. Immediately check the 'Start Pipeline/Build' button for pipeline before jenkins pod is not ready yet on these pages:
https://<master>:8443/console/project/<project>/browse/pipelines
https://<master>:8443/console/project/<project>/browse/pipelines/sample-pipeline

Actual results:
2. 'Start Pipeline/Build' button is not disabled

Expected results:
2. 'Start Pipeline/Build' button is better to be disabled

Additional info:

Comment 1 Jessica Forrester 2016-12-05 16:09:55 UTC

starting a pipeline build before jenkins is ready should never be a problem.  If you are seeing issues with that then we need a bug opened against the build component to track that.  I disagree with waiting for Jenkins to be ready before letting them start the pipeline.