Bug 1362270

Summary:	[RFE] Show what triggered a build
Product:	OpenShift Container Platform	Reporter:	Brennan Vincello <bvincell>
Component:	RFE	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED ERRATA	QA Contact:	Johnny Liu <jialiu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aos-bugs, erich, jokerman, misalunk, mmccomas, tdawson
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-09-27 09:42:09 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 Brennan Vincello 2016-08-01 19:10:09 UTC

RFE created to track release of: 
https://trello.com/c/wNcCnHPL/653-1-show-what-triggered-a-build

As an openshift user, we have builds with a mixture of git webhooks and ImageStream triggers. When new builds are triggered, we'd like to see what caused the new build.

Submitted on behalf of client.

Comment 1 Jessica Forrester 2016-08-01 20:50:38 UTC

Story is already implemented, just moving to correct tracking categories for RFE bugs

Comment 2 Miheer Salunke 2016-08-02 09:47:54 UTC

1. Proposed title of this feature request  

Feedback about which trigger caused a build to fire

3. What is the nature and description of the request?  


When we have a build with a mixture of git (webhook) and ImageStream triggers - how can we see which trigger caused the build to start?  I would expect something in the CLI or gui which highlights which trigger caused the build.

We would also like to know whether we can have openshift trigger some sort of output plugin which is able to send an email or update an chatroom with details when a new build is triggered or completed successfully or failed?


7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
https://trello.com/c/wozDHSJ2/717-8-track-reason-a-build-was-run-triggered

https://github.com/openshift/origin/pull/7518
    
10. List any affected packages or components.
builds,cli,webconsole.

Comment 5 errata-xmlrpc 2016-09-27 09:42:09 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-2016:1933