• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • cppncss-plugin
    • None
    • Hudson 1.346
      CppNCSS (plugin) 1.0-beta-4

      We recently installed the latest NCSS plugin onto Hudson 1.346. We followed the setup instruction as outlined on the plugin Wiki page (http://wiki.jenkins-ci.org/display/JENKINS/CPPNCSS).

      After we generated the cppncss.xml file and configure the job to point to the appropriate path, nothing happens. I don't see the plugin being run in the log file:

      [WARNINGS] Parsing warnings in console log...
      [WARNINGS] Found 64 annotations (0 new, 0 high, 64 normal, 0 low)
      [WARNINGS] Not changing build status, since no threshold has been exceeded
      Archiving artifacts
      Recording test results
      Recording fingerprints
      [DocLinks] Copying API Doxygen to 1 ...
      [DocLinks] Copying Security
      Doxygen to 2 ...
      ####################################################

        1. This is where I expect to see CppNCSS to run. ##
          ####################################################
          No emails were triggered.
          Finished: SUCCESS

      I even configured the logger to the package, but I didn't see any an message in the log.

      What am I doing wrong?

          [JENKINS-5697] CppNCSS 1.0-beta-4 plugin not working

          cchan_qa added a comment -

          Change the priority to blocker because we have the report CppNCSS.xml, but can't integrate it into Hudson.

          cchan_qa added a comment - Change the priority to blocker because we have the report CppNCSS.xml, but can't integrate it into Hudson.

          fmhome added a comment -

          I am having the same issue, can someone please take a look and reply.

          I don't see any activity on this at all.

          Thanks.

          fmhome added a comment - I am having the same issue, can someone please take a look and reply. I don't see any activity on this at all. Thanks.

          evernat added a comment -

          According to the issue the tested version is "CppNCSS plugin 1.0-beta-4", with beta in the name.
          But according to the wiki page, v1.0 (without beta in the name) and then v1.1 were released:
          http://wiki.jenkins-ci.org/display/JENKINS/CPPNCSS+Plugin

          Can you confirm that the issue still exists? Thanks

          evernat added a comment - According to the issue the tested version is "CppNCSS plugin 1.0-beta-4", with beta in the name. But according to the wiki page, v1.0 (without beta in the name) and then v1.1 were released: http://wiki.jenkins-ci.org/display/JENKINS/CPPNCSS+Plugin Can you confirm that the issue still exists? Thanks

          kutzi added a comment -

          No response from reporter -> closing

          kutzi added a comment - No response from reporter -> closing

          I am still experiencing this issue with the most current version of CppNcss (1.1):

          • No report is generated.
          • No errors are logged. I know the plugin must be getting invoked because I can trigger an error by giving an invalid path to the xml data file.

          Can someone please investigate this?

          Peter Gerstmann added a comment - I am still experiencing this issue with the most current version of CppNcss (1.1): No report is generated. No errors are logged. I know the plugin must be getting invoked because I can trigger an error by giving an invalid path to the xml data file. Can someone please investigate this?

            Unassigned Unassigned
            cchan_qa cchan_qa
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: