Bug 1324909

Summary:	Gathering developer metrics
Product:	OpenShift Container Platform	Reporter:	William Henry <whenry>
Component:	RFE	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	aos-bugs, jokerman, mmccomas, myllynen, sspeiche, trankin
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-10 17:25:24 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 William Henry 2016-04-07 14:43:31 UTC

Description of problem:

Openshift has traditionally being focused on the developer. Today the metrics gathering is focusing only on the containers and kubernetes components. 

In the future Openshift should also gather metrics on the developers. # commits, PRs, # of issues fixed etc. etc. 

Also helping connect containers to the commits could also help see which developers have the least amount of production problems so that they can help coach others on the team with less favorable "outages"  or issues associated with their code. 

So it's not just about container/pod/cluster health its about DevOps and how we can have less production issues by making developers more productive and better developers.   

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan McPherson 2016-04-13 13:03:02 UTC

We do connect the dev id and commit id to the build today if the build was based on source.  But some of this is a bit of a stretch to add to OpenShift given we don't really control the source code side of the equation.  Namely, # of commits, PRs, # of issues fixed.