MantisBT - CDash
View Issue Details
0008706CDashpublic2009-03-09 15:082009-03-09 15:08
Roscoe A. Bartlett 
 
normalfeaturehave not tried
newopen 
 
 
0008706: CDash Dev: Group moves and deletes of builds
Is there a short hand way to remove an entire set of these package builds from the dashbaord? I see that you can remove individual builds (when logged in as admin) but when you have 40+ packages that can take a bit of time to delete one at a time. How hard would it be to put in a button called something like 'Delete all shown builds' on the page:

    http://trilinos-dev.sandia.gov/cdash/index.php?project=Trilinos&display=project&date= [^]

?

Combined with the query capability, this would make it easy to remove entire sets of bad builds.

Note that these were 'vesper' builds listed as 'Nightly' builds so the only way to remove their impact on the overall project/subproject dashboard page at:

    http://trilinos-dev.sandia.gov/cdash/index.php?project=Trilinos [^]

is to remove all of these builds.

Actually, as an alternative to deleteing all of these builds in one shot, what if you could also move them to say the 'Junk' track? That we still keep a record that the build happened but it would not corrupt out overall project dashboard.

Note that catastrophic problems will occur on a platform like this once in awhile and it would be very helpful to be able to remove or move thse out of 'Nightly' or 'Continuous' tracks so that it does not corrupt the overall project dashboard.

Note that I am assuming that the basic filtering described in issue http://public.kitware.com/Bug/view.php?id=8592 [^] will be implemented which would allow us to only show 'Nightly' and/or 'Continuous' builds in the mail project/subproject summary dashbaoard.

This is not a high-priority issue for Trilinos since we can always delete do this one Trilinos package at a time. However, this would be a desirable feature because we will have to do this from time to time.
No tags attached.
Issue History
2009-03-09 15:08Roscoe A. BartlettNew Issue

There are no notes attached to this issue.