From: Gordon H. <gor...@ya...> - 2012-11-30 19:40:45
|
Hi, I am using cobertura for the first time. I'm trying to understand the right way to use it with Jenkins CI. We are writing a webapp. We have unit tests. Jenkins is setup to perform maven builds triggered by svn commits. The last step of a successful build is to deploy the generated war to a Tomcat instance for QA/demo purposes. I have Jenkins and the pom setup to run tests with cobertura. Jenkins shows lovely cobertura graphs :) My concern is that we should NOT be deploying the instrumented war to Tomcat. I do not need to track code coverage in the deployed environment. Tomcat should be running the app as may be released to production (ie. non-instrumented). But AFAIK there's only the one war being generated by the build. What's the right thing to do here? Am I mistaken about what the build generates? Is the solution to have separate projects running in Jenkins, one for cobertura and one for deploying to Tomcat? What do other people do? Gord |