Task #1320
closed
Code coverage builds on Jenkins
Added by Junxiao Shi over 10 years ago.
Updated over 10 years ago.
Description
Setup a Jenkins job that builds NFD on Ubuntu 12.04 64-bit with code coverage reporting.
This job should be triggered when a new patchset is uploaded, or when a draft patchset is published.
It MAY be included in existing verify job, if the increase of job execution time is less than 10%; otherwise, it SHOULD be a separate job with dedicated buildbots.
Code coverage results MUST be accessible on Jenkins web UI.
The comment onto Gerrit SHOULD include the overage code coverage and a link to view detailed code coverage reports.
Code coverage MUST NOT affect "Verified" score.
I don't think Gerrit Trigger Plugin for Jenkins supports customize message to post result from Cobertura Plugin. The build link we currently have will lead to the Jenkins build page on which there will be detailed code coverage report if we configure the code coverage check in the same job.
In my opinion, code coverage is an advisory check, and it should not be part of the same job. Going to jenkins to check the data is kind of strange...
Then should I set up an separate job to check it? The new job is going to post its link on gerrit as well.
I prefer to have it in the same job, if the increase of build time is less than 10%.
Otherwise it's too many emails.
20140316 conference call decides that code coverage should be enabled on Ubuntu 12.04 slave in the same job.
It's an advisory check and should not affect success/failure score.
Please proceed with the deployment.
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
Code coverage check for ndn-cpp-dev and NFD is up.
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by