I'm using simian to find duplicates in our source code. The result of simian is an xml file that stats where duplicate code is found. It tells the start and end line of each block of duplicate code. So lets say build 5 has generated a simian result file. Now someone checked something in which triggers build 6. In one of the publisher tasks, I'd like to compare simian result from build 6 against simian result build 5. If there is an additional block of dupplicate code, I'd like to fail the build. So I must have a way to compare the result fails. This could be helpfull for other result files as well, e.g. FxCop. So I wonder if someone has done something like this before?
On Jan 8, 2:39 pm, "Ruben Willems" <[email protected]> wrote: > Hi > > just press sent to quickly :-( > you have to copy the code also to folder X > do this only AFTER the task of comparing, > so when someone does an attempt of removing the duplicate, > it is still compared with source that was ok. > > that should do it > > with kind regards > Ruben Willems > > On Thu, Jan 8, 2009 at 7:32 PM, [email protected] <[email protected] > > > wrote: > > > Hi, > > is there a way to compare the build results of the previous build with > > the current build using a publisher? I'm using simian to find > > duplicate lines of code and would like to fail the build if someone > > checks in code that has duplicates. Since we have a huge code base, we > > are not going to cleanup all the existing code, but I would like to > > improve the code quality over time and would not allow to have code > > being checked in that make it worse. Has anyone tried to compare the > > results and fail a build based on that?
