![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Manuel Carrasco
|
|
Components:
|
performance-plugin |
|
Created:
|
03/Nov/14 2:57 PM
|
|
Description:
|
The time it takes for a Jenkins based build pipeline to pump artifacts from source code into deployed applications matters to most agile and less agile teams and there is a phletora of attemtps underway in many organizations to "improve build time".
Just there is no objective criteria at all to tell if the time it takes for a build to be processed is accetable or not. If your build takes e.g. 45 minutes, is that good or bad?
Any especially there is hardly any criteria to compare hardware in terms of build performance, so there is little chance to find out if your build times would shorten if you move from VMs to phyiscal hardware, if you add more RAM, if you add slaves, if you upgrade the VCS server, ...
Microsoft provides something very simple (to reads, talk about and compare) with the Windows Experience Index (WIE).
Jenkins might be the natural component to perform such measurements in build pipeline as Jenkins is usually the controller which coordinates and thus would be able to measure amounts and time of VCS checkouts / updates, compilation and artifact deployment.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Torsten Schlabach
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
