MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006371CDashpublic2008-02-18 12:072008-04-28 09:16
ReporterFrançois Bertel 
Assigned ToJulien Jomier 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version1.0 
Summary0006371: Having the number of nightly changes on the main page
DescriptionAt the top of the page, where there is a link "Nightly Changes", it would be nice to see the number of changes as we used to see in the old dart.

When you browse pages day by day, it is quick to see if there was any relevant change for a specific day.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-02-18 12:07François BertelNew Issue
2008-02-18 17:00David ColeNote Added: 0010554
2008-02-18 21:12Bill HoffmanStatusnew => assigned
2008-02-18 21:12Bill HoffmanAssigned To => Julien Jomier
2008-02-19 13:32Bill LorensenNote Added: 0010592
2008-02-29 11:25François BertelNote Added: 0010669
2008-04-28 09:16Julien JomierStatusassigned => closed
2008-04-28 09:16Julien JomierNote Added: 0011566
2008-04-28 09:16Julien JomierResolutionopen => fixed
2008-04-28 09:16Julien JomierFixed in Version => 1.0

Notes
(0010554)
David Cole   
2008-02-18 17:00   
It would be nice, but it would not be fast... We would have to cache the number in a database table (per project, per day) to make this fast. And it will still be slow (as slow as clicking on the link) the first time it executes unless we have something that pre-populates that database table (per project, per day) right after each project's nightly start time ticks by...
(0010592)
Bill Lorensen   
2008-02-19 13:32   
To Dave's point regarding speed, clicking on the current "Nightly Changes" on the ITK dsshboard is very slow(sometimes over 30 seconds). I suggest elimination of this link. The nightly builds themselves already report the updated files as part of their submission process.

Another alternative would be to generate a static page for that olink since it only changes once each day.
(0010669)
François Bertel   
2008-02-29 11:25   
The nightly builds themselves only report the very last updated files as part of their submission process.

The Nightly Changes link reports more relevant information than that: list of all changes on files during a day and in any branch. Imaging you commit two changes on a file during the day, the first one with a major bug fix and the second one with a minor typo, only the second one is displayed on the nightly builds, whereas all of them are displayed on the Nightly Changes link.

Another limitation of nightly builds is sometimes some machines don't submit for a day, a week or more for any reason (maintenance, power outage, ...). When they start to submit again, they first perform an update with the repository and the number of updates for a particular build are the changes that happen between
the two submission dates that are way apart, not the changes for the last 24 hours on the repository. The build will report maybe changes on 100 files for a day when the actual activity for the day on the repository was about changes on 10 files.

Generating a static page sounds like the right solution to me.
(0011566)
Julien Jomier   
2008-04-28 09:16   
Fixed in 1.0.
Now the first build of the day trigger the lookup for updates and store the updates in the database. If curl support for PHP exists then this is done asynchronously otherwise the action is synchronous.