On Fri, Dec 12, 2008 at 10:21 AM, PilotBob <[email protected]> wrote: > > On Dec 11, 6:18 pm, "Jon W" <[email protected]> wrote: >> would be nice if it would would list the project(s) broken, and the >> possible developer(s) who broke the build. An added bonus would be >> some statistics of who breaks the build the most as to shame the bad >> developers. > > Not sure I'd want to work at a place that does this.
Ok. > I'm sure you could customize the dashboard to show this. But, how do > you know who broke the build? Many times out builds consist of > multiple changesets checked in by various devs. That is why it would be nice to list all developers who checked in. The information is all there... > You might also want to consider doing isolated builds in a dev branch > then merging the results into trunk if it doesn't fail. Then you can > see how many times the build broke on each branch. > > Once again, I think positive reinforcement is better than negative > reinforcement. Sure, but when that fails some people need to see how people with good development habits work. The person who breaks the build the least gets a shiny toy. -Jon
