[From Aaron]
Hey guys,
I have a suggestion concerning the Build drill down section in the Daily Project Details analysis. It goes like this....
In addition to the current "Builds by Member" drill down section, I propose new a section that shows "Type of Build by Member" drill down. This information would be extremely useful to determine if people are running checkstyle, unit tests, compiling, etc. For example, if someone fails the build with a checkstyle error we can immediately pull up the Daily Project Details analysis and see if they even invoked checkstyle.
I just realized a better idea. After a build failure is sensed and sent to Hackystat, we could access a SDSA (Software Development Stream Analysis) analysis that creates episodes delimited by a CommitTokenizer for any member working in the failing module. With this analysis we can see their SDSA Actions before the commit. Currently this analysis would have to be time delayed because the Commit sensor works only once a day, but you get the point. This Episode can be flagged, for future Build Failure Analysis. For example, after a large-enough data set of SDSA "Commit-Related Build Failure" episodes and the Build Results are collected, then a SDSA Classifier (a Jess Rule) can be implemented and used in analysis.
Sorry for the thinking aloud, but of course, I just had another better idea. If we had a real-time Commit Sensor, then SDSA can be fired automatically when a commit occurs to classify the set of actions as a potential "Commit-Related Build Failure Episode". And, if the SDSA Clasifier identified an episode as a potential build failure, then an alert should be triggered. This basically equates to iSEE, which is really cool. Although, this may not make too much sense in CSDL development, this makes perfect sense for large and complicated software development processes such as MDS, where their main problem is build failures, which can set them back hours or even days. There's your 10x.
This of course got me thinking about iSEE. I imagine an iSEE framework that allows different Intelligent-Adaptive-Autonomous (IAA) components to be plugged into the iSEE framework. Each component is built specifically for certain Software Development problems. In this email, I might have just described the "Commit-Related Build Failure" iSEE IAA component.
wow... Anyway, lets just start with adding the "Type of Build by Member" drill down in the Daily Project Details analysis. Although, this might be a little harder than I thought because the Daily Project Details mechanism only supports one drill down section for a given DailyProjectData class.
thanks, aaron
[I like this idea but maybe for release 6.5? 6.6? 8.8? :-)]
