We're updating the issue view to help you get more done. 

As a krb5 developer, I want to investigate the Travis-Coverity integration so I can decide whether it's appropriate for us

Description

Our current Coverity Scan builds occur multiple times per week out of buildbot. There is a new integration that allows Coverity Scan to link to a GitHub repository, as well as one that allows Travis CI to submit builds to Coverity Scan.

Drawbacks include Coverity Scan's lack of accommodation for branches; its defect tracking for new and resolved defects implicitly assumes a single branch of development. There is a maximum rate of build submissions per week, so monitoring the master branch isn't appropriate. Coverity's recommended approach is to use a dedicated "coverity_scan" branch, but that would require manual developer work to update given our version control current setup.

Status

Assignee

Unassigned

Reporter

Tom Yu

Labels

None

Priority

Normal