I've been playing with that idea also, but have not done it yet a lot of logic goes into that, and what would be a good consensus?
so a win for all. any ideas appreciated with kind regards Ruben Willems On 27 March 2014 15:53, Tiny Montgomery <[email protected]> wrote: > Hi, > > I'm using the statistics publisher but its really lacking in > functionality. Has anyone developed anything that compiles good build over > build stats? Like specifically I would like to know which tests are the > most unstable. Right now the mentality is if a test passes it works and if > it passed on the previous build and then fails on a sequential build with > no changes its the builds fault aka...my build scripts. I would love to > have a report that says this test fails 35% of the time or whatever it > happens to be. I really don't want to have to build this from scratch > though; I find it hard to believe that no one else hasn't done something > like this already. > > Thanks, > > Mont > > -- > > --- > You received this message because you are subscribed to the Google Groups > "ccnet-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "ccnet-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
