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

BZ 97113 - Provide support of Coverity runs from Workflow plugin

XMLWordPrintable

      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

          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

          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

          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

          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.

          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.

          karthik paidi added a comment -

          hope will get an update on this issue soon and oleg_nenashev sgardell  could you share some details on how you are publishing the coverity results without pipline plugin support if you are publishing coverity defects onto a dashboard

          karthik paidi added a comment - hope will get an update on this issue soon and oleg_nenashev sgardell   could you share some details on how you are publishing the coverity results without pipline plugin support if you are publishing coverity defects onto a dashboard

          Oleg Nenashev added a comment -

          karthik546 see my comment above. In several cases I was just using custom Docker images with all the stuff I needed. Effectively, I was using low-level CLI calls

          Oleg Nenashev added a comment - karthik546 see my comment above. In several cases I was just using custom Docker images with all the stuff I needed. Effectively, I was using low-level CLI calls

          Joel Briggs added a comment -

          Support for running Coverity in a Jenkins Pipeline has been added in release 1.10.0 with the pipeline steps `coverityResults` and `withCoverityEnv`. Coverity tools have been moved to a 'ToolInstallation' (Global Tool Configuration) and can be used with the 'tool' step.

          The decision was made to create an entirely new publisher (coverityResults) instead of re-working the existing CoverityPublisher (which does quite a bit more than get results from Coverity Connect). The new publisher only retrieves issues from a configured Coverity Connect Instance, Project, and View (filtering would be done within the Coverity Connect UI).

          The build, analyze, commit commands are no longer automatically run, but tools can be scripted when accessed through the 'withCoverityEnv' or 'tool' steps.

          See https://github.com/jenkinsci/coverity-plugin#pipeline-setup for complete details

          Joel Briggs added a comment - Support for running Coverity in a Jenkins Pipeline has been added in release 1.10.0 with the pipeline steps `coverityResults` and `withCoverityEnv`. Coverity tools have been moved to a 'ToolInstallation' (Global Tool Configuration) and can be used with the 'tool' step. The decision was made to create an entirely new publisher (coverityResults) instead of re-working the existing CoverityPublisher (which does quite a bit more than get results from Coverity Connect). The new publisher only retrieves issues from a configured Coverity Connect Instance, Project, and View (filtering would be done within the Coverity Connect UI). The build, analyze, commit commands are no longer automatically run, but tools can be scripted when accessed through the 'withCoverityEnv' or 'tool' steps. See https://github.com/jenkinsci/coverity-plugin#pipeline-setup for complete details

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

              Created:
              Updated:
              Resolved: