Bug 1608715

Summary:	No build history limit when describe pipeline build
Product:	OpenShift Container Platform	Reporter:	Wenjing Zheng <wzheng>
Component:	Build	Assignee:	Corey Daley <cdaley>
Status:	CLOSED ERRATA	QA Contact:	Wenjing Zheng <wzheng>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.11.0
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:	2018-10-11 07:22:15 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:
Embargoed:

Description Wenjing Zheng 2018-07-26 08:11:00 UTC

Description of problem:
There is no "successfulBuildsHistoryLimit" and "failedBuildsHistoryLimit" when describe build after adding them.

Version-Release number of selected component (if applicable):
v3.11.0-0.9.0

How reproducible:
always

Steps to Reproduce:
1.Create a pipeline build
$oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/pipeline/samplepipeline.json 
2. oc patch   bc/sample-pipeline  -p '{"spec": {"successfulBuildsHistoryLimit": '3', "failedBuildsHistoryLimit": '2'}}'
3. Describe buildconfig

Actual results:
There is no info about "successfulBuildsHistoryLimit" and "failedBuildsHistoryLimit"

Expected results:
For better user experience, the options should exist.

Additional info:

Comment 1 Corey Daley 2018-08-06 16:04:47 UTC

Submitted pull request: https://github.com/openshift/origin/pull/20548

Comment 2 Corey Daley 2018-08-07 13:32:18 UTC

Pull request has been merged.

Comment 4 Wenjing Zheng 2018-09-06 06:28:33 UTC

Verified with below version:
oc v3.11.0-0.28.0
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Builds History Limit:
	Successful:	3
	Failed:		0

Comment 6 errata-xmlrpc 2018-10-11 07:22:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2652