[ 
https://issues.jenkins-ci.org/browse/JENKINS-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158630#comment-158630
 ] 

Todd Patterson commented on JENKINS-1327:
-----------------------------------------

+1  Just voted for this.

We recently migrated to Jenkins v1.431 from Quickbuild.  The "Build Time Trend" 
graph is a very useful feature, but like the reporter stated, it only 
represents those builds which still exist.  Any builds which have been 
purged/cleaned-up will not be shown on the graph.

Instead of statically defining a window (e.g 30 days or 30 builds), we would 
very much like the ability to configure the number of builds that the graph 
includes.  I realize the graph could become very compressed if too many builds 
were included, so perhaps a ceiling/max-value could be enforced on the 
configuration.

Please let me know if I should file this as a separate request, seemed fitting 
to include as part of this issue.
                
> Alternate build time trend graph
> --------------------------------
>
>                 Key: JENKINS-1327
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-1327
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: other
>    Affects Versions: current
>         Environment: Platform: All, OS: Linux
>            Reporter: tblack
>
> I would be interested in seeing an alternate presentation of the existing 
> build
> time trend graph.  The alternative graph would have two differences:
> 1.) I would like to see a historical 30-day presentation, even if the job has
> explicitly been marked to keep only smaller number of builds or shorter days
> worth of builds.
> 2.) The X-axis would be time-normalized.  That is, if a job has not be 
> triggered
> for 5 days, I would see that time gap show up on the graph.
> I think the current graph gets its data from the 'builds' directory of the job
> workspace, so to accomplish number the above, there would have to be an
> additional persistence mechanism to hold the build number, timestamp and build
> duration.
> It would also be valuable to have a direct link to the graph (same as the
> existing graph).  Perhaps something like: 
> http://hudson-host:8080/job/my-job/buildTimeGraph30Day

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to