Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32354

BZ 97113 - Provide support of Coverity runs from Workflow plugin

      Desired functionality:

      • Coverity publisher implemented as a SimpleBuildStep
      • Publishing of reports in workflow runs

          [JENKINS-32354] BZ 97113 - Provide support of Coverity runs from Workflow plugin

          Oleg Nenashev created issue -

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/2637aebf1e721a2f5e492530d7b796b34306c455 Log: JENKINS-32353 JENKINS-32354 JENKINS-32355 Merging #293. Compare: https://github.com/jenkinsci/workflow-plugin/compare/5f392fbd9b2a...2637aebf1e72
          Patrick Wolf made changes -
          Epic Link New: JENKINS-34657 [ 170293 ]
          Sverre Moe made changes -
          Labels Original: workflow New: Pipeline workflow
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 167966 ] New: JNJira + In-Review [ 182917 ]
          Andrew Bayer made changes -
          Labels Original: Pipeline workflow New: Pipeline pipeline workflow
          Andrew Bayer made changes -
          Labels Original: Pipeline pipeline workflow New: Pipeline pipeline

          Tom Bamford added a comment -

          Hello kdang, frossi,

          I don't suppose you folks will get a chance to look at this at some point?

          Tom Bamford added a comment - Hello kdang , frossi , I don't suppose you folks will get a chance to look at this at some point?

          Oleg Nenashev added a comment -

          rocketeer125 AFAIK no progress by now.
          I'm using Docker Pipeline plugin with images like https://github.com/oleg-nenashev/docker-coverity-scan-maven as a workaround, but actually such approach does not integrate reporting into Jenkins

          Oleg Nenashev added a comment - rocketeer125 AFAIK no progress by now. I'm using Docker Pipeline plugin with images like https://github.com/oleg-nenashev/docker-coverity-scan-maven as a workaround, but actually such approach does not integrate reporting into Jenkins

          I think the most value would come from focusing on recovery of issues from the Coverity Connect database as the mechanics of getting code scanned and results uploaded to Coverity Connect are quite straight-forward.

          Steven Gardell added a comment - I think the most value would come from focusing on recovery of issues from the Coverity Connect database as the mechanics of getting code scanned and results uploaded to Coverity Connect are quite straight-forward.

            jbriggs Joel Briggs
            oleg_nenashev Oleg Nenashev
            Votes:
            13 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated:
              Resolved: