Uploaded image for project: 'I&AM Kerberos'
  1. KRB-44

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

    Details

    • Type: Story
    • Status: To Do (View workflow)
    • Priority: Normal
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: None
    • Components: None
    • Labels:
      None
    • Sprint:

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tlyu Tom Yu (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Who's Looking?