• 5.0.0 (analysis-model and warnings-ng)

      Step
      recordIssues tool: mavenConsole(),
                   filters: [excludeType('maven-surefire-plugin:test'),
                             excludeMessage('.*A new version of dependency-check is available.*')],
                   qualityGates: [[threshold: 1, type: 'TOTAL', unstable: true]]
      
      Console (643-649)
      [INFO] --- dependency-check-maven:4.0.2:check (default) @ logger-tcp-server ---
      [INFO] Central analyzer disabled
      [INFO] Checking for updates
      [INFO] Skipping NVD check since last check was within 4 hours.
      [WARNING] A new version of dependency-check is available. Consider updating to version 5.0.0.m2.
      [INFO] Skipping RetireJS update since last update was within 24 hours.
      [INFO] Check for updates complete (31 ms)
      

          [JENKINS-56526] excludeMessage does not match description text

          James Howe created issue -

          Hi,

          I think I'm running into the same issue here. The following problem occur with the warnings-ng-plugin:

          I'm building our documentation through a pipeline script and I  get a doxygen generated log named "doxygen-warnings.log". In Jenkinsfile I've configured to look for

          recordIssues filters: [excludeMessage('.*warning: no uniquely matching class member found for*.'), excludeFile('.*\\/BLABLA\\/.*|.*\\/BLABLA\\/.*|.*\\/STM32F4xx\\/.*')], tools: [doxygen(pattern: 'doxygen-warnings.log')]

          I used the "Pipeline Syntax Generator" for this line. Unfortunatelly, the Plugin does not find anything. Even when I search some parts of the message in the plugin when viewing the summary.

           

          The output of doxygen which I want to filter looks like this:

          /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:13: warning: no uniquely matching class member found for
          template <>
          template <>
          const hal_pcba::Uart1::SingleConfig Uart1::configuration(hal_uc::Uart::Baudrate::BAUD_38400, hal_uc::Uart::WordLength::LEN_9, hal_uc::Uart::StopBits::BIT_1, hal_uc::Uart::Parity::EVEN, hal_uc::Uart::Mode::TX_RX, hal_uc::Uart::FlowControl::NONE, hal_uc::Uart::Oversampling::X16)

          /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:27: warning: no uniquely matching class member found for
          template <>
          template <>
          const hal_pcba::UartRxPin::SingleConfig hal_pcba::UartRxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance)

          /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:35: warning: no uniquely matching class member found for
          template <>
          template <>
          const hal_pcba::UartTxPin::SingleConfig hal_pcba::UartTxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance)

           

          When I test my RegEx at https://regex101.com/ I get the right results. Do I need any special RegEx Magic? Is this a known Bug?

           

          Kind regards

          Andreas

           

           

           

           

           

          Andreas Zeiler added a comment - Hi, I think I'm running into the same issue here. The following problem occur with the warnings-ng-plugin: I'm building our documentation through a pipeline script and I  get a doxygen generated log named "doxygen-warnings.log". In Jenkinsfile I've configured to look for recordIssues filters: [excludeMessage('.*warning: no uniquely matching class member found for*.'), excludeFile('.*\\/BLABLA\\/.*|.*\\/BLABLA\\/.*|.*\\/STM32F4xx\\/.*')] , tools: [doxygen(pattern: 'doxygen-warnings.log')] I used the "Pipeline Syntax Generator" for this line. Unfortunatelly, the Plugin does not find anything. Even when I search some parts of the message in the plugin when viewing the summary.   The output of doxygen which I want to filter looks like this: /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:13: warning: no uniquely matching class member found for template <> template <> const hal_pcba::Uart1::SingleConfig Uart1::configuration(hal_uc::Uart::Baudrate::BAUD_38400, hal_uc::Uart::WordLength::LEN_9, hal_uc::Uart::StopBits::BIT_1, hal_uc::Uart::Parity::EVEN, hal_uc::Uart::Mode::TX_RX, hal_uc::Uart::FlowControl::NONE, hal_uc::Uart::Oversampling::X16) /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:27: warning: no uniquely matching class member found for template <> template <> const hal_pcba::UartRxPin::SingleConfig hal_pcba::UartRxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance) /home/jenkins/workspace/Documentation_SCM/Src/HAL_PCBA/Conf/com_conf.cpp:35: warning: no uniquely matching class member found for template <> template <> const hal_pcba::UartTxPin::SingleConfig hal_pcba::UartTxPin::configuration(hal_uc::Uart::Pin::IoMode::ALTERNATIVE_PP, hal_pcba::UartInstance)   When I test my RegEx at https://regex101.com/ I get the right results. Do I need any special RegEx Magic? Is this a known Bug?   Kind regards Andreas          

          Ulli Hafner added a comment -

          The reason is that maven warnings do not have a message. The matching lines are set into the description attribute.

          I'm not sure if it makes more sense to change that and set the message property or if it would be better to match message and description by the filter.

          Ulli Hafner added a comment - The reason is that maven warnings do not have a message. The matching lines are set into the description attribute. I'm not sure if it makes more sense to change that and set the message property or if it would be better to match message and description by the filter.
          Ulli Hafner made changes -
          Epic Link New: JENKINS-56456 [ 198054 ]

          Ulli Hafner added a comment -

          I think the best way would be to let the filter work on both description and message. These values are indistinguishable for a user. Only the implementation details actually work on the individual properties.

          Ulli Hafner added a comment - I think the best way would be to let the filter work on both description and message. These values are indistinguishable for a user. Only the implementation details actually work on the individual properties.
          Ulli Hafner made changes -
          Component/s New: analysis-model [ 23523 ]
          Component/s Original: warnings-ng-plugin [ 24526 ]
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Labels New: help-wanted newbie-friendly
          Summary Original: Cannot get excludeMessage to work New: excludeMessage does not match description text
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          Ulli Hafner made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Ulli Hafner made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          Ulli Hafner made changes -
          Rank New: Ranked higher

            drulli Ulli Hafner
            jameshowe James Howe
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: