Home/ Questions/Q 8513015
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T04:26:18+00:00

I have Cobertura integrated with my project, and it works as expected. However, I

  • 0

I have Cobertura integrated with my project, and it works as expected. However, I am not sure which of the Cobertura artifacts to check-in to SVN.

The directory structure looks something like:

  • MainProjectDir
  • cobertura.ser
  • coberturaDir
    • cssDir
    • imagesDir
    • instrumentedDir
    • js
    • reports
    • LOTS OF html FILES

There is just over 1 MEG of space in the coberturaDir, and checking in that directory seems troublesome for future commits.

My goal is to keep track of the total for the project and each class.

Of the cobertura artifacts, what should I be committing to SVN?

Thanks,
Sean

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    None of them.

    You should be able to regenerate the Cobertura reports by pointing toward an older revision in your version control system. Since the reports are a derivative product of the version of software, there’s no need to store them. This is the same principle that applies to generated documentation (javadoc, doxygen) and binary files produced from your source code (jars, exes, class files).

    If you need history, I’d suggest saving the report outside of version control, in someplace like a file server. You can then compress old report directories into ZIPs or tarballs so they are available, but archived to reduce space and make finding the latest data easier. You can also take the measurements and metrics that are most important and put them into a single file, such as a spreadsheet, and put that in a file server.

    • 0