Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how do I get historyThreshold to work

I have configured maven witht he clover plugin and I REALLY like it so far. But I seem to have issues with the <historyThreshold/> tag.

This is my configuration:

<configuration>
<licenseLocation>/Users/bclarance/Downloads/clover.license</licenseLocation>
<!-- How to specify the coverage threshold -->
<targetPercentage>70%</targetPercentage>
<!-- How to specifiy historical threshold -->
<historyThreshold>1%</historyThreshold>
<!-- How to specify what typeds of reports to generate -->
<generateJson>true</generateJson>
<generatePdf>true</generatePdf>
<generateXml>true</generateXml>
<generateHtml>true</generateHtml>
<!-- how to evaluate coverage -->
<instrumentation>statement</instrumentation>
<!-- when using context you have to add the filters -->
<contextFilters>private,log</contextFilters>
<!-- how to generate historical code coverage and define a dir for it -->
<generateHistorical>true</generateHistorical>
<historyDir>${user.home}/history/${project.artifact}</historyDir>
</configuration>

When I build my clover report at 90% code covereage and then build a subsequent one 85% I would expect it to fail, but it doesn't. Firstly, becasue it meets the targetPErcentage, but I still need it to fail if there is a code coeverage drop too large, in this case only 1% to validate the failure.

Pelase help if you have any ideas.

Bilal

1 answer

0 votes

Hi Bilal,

Please have a look at documentation of historyDir and historyThreshold attributes:

Allows you to specify a location for historical build data, along with a configurable threshold expressed as a percentage used to cause the build to fail if coverage has dropped. This attribute is passed down to specified packages, then the same test is done for these at the package level. This will only be used if there is no targetPercentage parameter set.

As you can see you cannot use targetPercentage and historyThreshold in the same configuration. However, you can create two separate profiles with different configurations:

  • one for clover2:check with targetPercentage defined
  • one for clover2:check with historyThreshold defined

This will work.

Regards
Marek

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

173 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you