MantisBT - CDash | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0010909 | CDash | public | 2010-06-29 14:59 | 2010-06-29 14:59 | |
| Reporter | Bill Hoffman | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Summary | 0010909: Blame button | ||||
| Description | It would be cool if CDash had a "blame" button. The button would show up when there was a failed test, warning, build error, etc. You click on it and it takes you to a page that has: 1. link to the day when that failure was not happening. 2. A diff of all things that have changed from the day where the failure happened, and the day when it did not happen. - diff Notes (see if build script changed) - diff all test output ( see if test output changed) - show updates ( what files changed ) - diff configure output ( might show a compiler/sys change) I am thinking this would be a quick way to find out who/what broke something. Pretty much this would do automatically what we do by hand. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-06-29 14:59 | Bill Hoffman | New Issue | |||
| There are no notes attached to this issue. |