It would make sense to add a help text in the pipeline steps description for the filter regexp values.

      Reason:

      I am using the warnings plugin for the quality checker

      But I want it to record quality checks for the warnings belongs to only specific files or exclude specific files warnings

      I tried the Inclu and exclude files filter but I am getting count as zero even the warnings for the files are present in include and exclude also I am getting zero when I removed othe files

        1. screenshot-1.png
          screenshot-1.png
          71 kB
        2. screenshot-2.png
          screenshot-2.png
          20 kB
        3. screenshot-3.png
          screenshot-3.png
          6 kB

          [JENKINS-67759] Add help for all step options

          Ulli Hafner added a comment -

          The text in the filter expects a regular expression. You are providing a string of files separated by comma, this will never match a file.

          Ulli Hafner added a comment - The text in the filter expects a regular expression. You are providing a string of files separated by comma, this will never match a file.

          krishna added a comment -

          I have got example for the old version to give filenames as in

          includePattern: '*/app_iface.c,*/app_iface_QM.c,*/Appl_Core0.c,*/Appl_Core1.c,*/Appl_Core2.c,*/Appl_Core3.c,*/Appl_Core3_QM.c,*/Appl_Core4.c,*/Appl_Etm.c,\
          */Appl_HSI_If.c,*/Appl_Rtm.c,*/Appl_SleepWakeup_If.c,*/ApplCan_RxSigProcess.c,*/Aptiv_CdcClient_Wrapper.c,*/Aptiv_CDD_TimeSync.c,\
          */Aptiv_Client_SWC.c,*/Aptiv_Comm_Mgr.c,*/Aptiv_Diag_Supplier_Notify.c,*/Aptiv_DiagMgr.c,*/Aptiv_Dlog_HweTable.c,\
          */Aptiv_E2E.c,*/Aptiv_Error_Manager.c,*/Aptiv_Eth_E2E_Msg_GW_PCAN.c,*/Aptiv_ETS_SWC.c,*/aptiv_f360_oal_adaptation_wrapper.cpp,\
          */Aptiv_Fas_Can_Timeout.c,*/Aptiv_Fascan_E2E_Gw_Msg_Read.c,*/Aptiv_IPsec_SWC.c,*/Aptiv_lbist_ram.c,*/Aptiv_MCAL.c,*/Aptiv_Pcan_Timeout.c,\
          */Aptiv_Safety_Manager.c,*/Aptiv_SafetyCoding.c,*/Aptiv_Security_Mgr.c,*/Aptiv_Server_SWC.c,*/Aptiv_SleepWakeup.c,*/Aptiv_SleepWakeup_Eth.c,\
          */Aptiv_SMU.c,*/aptiv_tracker_out_to_vru_input.c,*/Aptiv_Wdg_Manager.c,*/aptiv_wrapper_vru.cpp,*/Aptiv_XCP_SWC.c,*/aptive_wrapper_vru_fusion.cpp,\
          */Blu_HardwareAdapter.c,*/Blu_UserAdapter.c,*/CED_statemachine.c,*/Collect_PCAN_Data.cpp,*/core_timing_log.c,*/Core_Wrapper_F360Tracker.cpp,\
          */Cpu_Load.c,*/CTA_statemachine.c,*/Dlog_SweTable.c,*/f360_tracker_globals.cpp,*/f360_tracker_main.cpp,*/Fault_Manager.c,*/fixmac.c,\
          */freespace_statemachine.c,*/Internal_Faults.c,*/LCDA_statemachine.c,*/main.c,*/MainWrapper.c,*/Os_Callout_Stubs.c,*/Prog_CryptoAdapter.c,\
          */Prog_UserAdapter.c,*/qualifiers.c,*/RECW_statemachine.c,*/scw_statemachine.c,*/Startup_Safety.c,*/TA_statemachine.c,*/TrackerOutToFF.c,\
          */UDP_CAL_Logging_Buffer.c,*/UDP_FFOut_Logging_Buffer.c,*/UDP_logging_data.c,*/UDP_TrackerIAL_Logging_Buffer.c,\
          */UDP_TrackerInternal_Loggng_Buffer.c,*/UDP_TrackerOAL_Logging_Buffer.c,*/UDP_VRU_ML_Logging_Buffer.c,*/VTC_Manager.c,\
          */Wrapper_F360Tracker.cpp,*/Wrapper_F360Tracker_IAL_Ping.cpp,*/Wrapper_F360Tracker_IAL_Pong.cpp,*/Wrapper_F360Tracker_IAL_Pong_Backup.cpp,\
          */Wrapper_F360Tracker_OAL_Ping.cpp,*/Wrapper_F360Tracker_OAL_Pong.cpp,*/Wrapper_FF.c,\
          */app_iface.h,*/Appl_Core0.h,*/Appl_Core3.h,*/Appl_HSI_If.h,*/Appl_Rtm.h,*/Appl_SleepWakeup_If.h,*/ApplCan_RxSigProcess.h,\
          */Aptiv_CDD_TimeSync.h,*/Aptiv_Client_SWC.h,*/Aptiv_Comm_Mgr.h,*/Aptiv_Diag_Supplier_Notify.h,*/Aptiv_DiagMgr.h,*/Aptiv_Dlog_HweTable.h,\
          */Aptiv_E2E.h,*/Aptiv_Error_Manager.h,*/Aptiv_MCAL.h,*/Aptiv_Safety_Manager.h,*/Aptiv_SafetyCoding.h,*/Aptiv_Security_Mgr.h,\
          */Aptiv_SleepWakeup.h,*/Aptiv_SleepWakeup_Eth.h,*/Aptiv_SMU.h,*/aptiv_vru_ial.h,*/Aptiv_Xcp.h,*/Blu_HardwareAdapter.h,*/Blu_UserAdapter.h,\
          */CED_statemachine.h,*/Collect_PCAN_Data.h,*/core_timing_log.h,*/Cpu_Load.h,*/CTA_statemachine.h,*/f360_tracker_globals.h,*/f360_tracker_IAL.h,\
          */FaultManager.h,*/FeatureFunction_IAL.h,*/FeatureFunction_OAL.h,*/freespace_statemachine.h,*/Internal_Faults.h,*/LCDA_statemachine.h,\
          */macros.h,*/Prog_CryptoAdapter.h,*/Prog_UserAdapter.h,*/qualifier.h,\
          */radar_ecu_internal_CORE1.h,*/radar_ecu_vru_classifier.h,*/RECW_statemachine.h,*/scw_statemachine.h,*/TA_statemachine.h,\
          */Tracker_OAL.h,*/TrackerOutToFF.h,*/UDP_CAL_Logging_Buffer.h,*/UDP_FFOut_Logging_Buffer.h,*/UDP_logging_data.h,\
          */UDP_TrackerInternal_Loggng_Buffer.h,*/VTC_Manager.h,*/Wrapper_F360Tracker.h,*/Wrapper_FF.h,\
          */crc32.c,*/recog_side_radar_field_of_view.c,*/Wrapper_FF.c,*/FF_Statistic_Data.c,*/ac_get_pointer.c,\
          */tracker_f360_internal_logging.cpp,*/Output_Conv_Wrapper_F360Tracker.cpp,*/object_list_time_stamp.cpp,\
          */McalLib.c,*/Bmhd.c,*/Aptiv_Dlog_HweTable.c,*/Bm_UserAdapter.c,*/Blu_HardwareAdapter.c,*/Blu_UserAdapter.c,\
          */Dlog_SweTable,*/DcmFbl_UploadServices,*/Crypto_CertificateManagement,*/Aptiv_HAM.c,*/Aptiv_HAM.h,*/Aptiv_Dlog_HweTable.c,*/Prog_UserAdapter.c,\
          */Prog_HardwareAdapter.c,*/Dcm_Prog_Glue.c,*/BswM_Callout_Stubs.c,*/Aptiv_Diag_Supplier_Notify.c,*/Prog_CryptoAdapter.c,\
          */CtCDDRtMeas_OS.c,*/CtCDDRtMeas_User.c,*/CtCDDRtMeas_OS.h,*/CtCDDRtMeas_User.h',\
                                  messagesPattern: '',
                                  unHealthy: ''
          

          But I can't give the filename similar in the new one since I getting as

          I understand it will accept only regular expressions but I can't give the filenames in that way. I also have no knowledge of regular expression

          I asked my colleague for help but he wasn't able to give a regular expression for the filenames.

          Please provide if exists any other way to give filenames
          or an example of how I can give regular expressions for these file names

          krishna added a comment - I have got example for the old version to give filenames as in includePattern: '*/app_iface.c,*/app_iface_QM.c,*/Appl_Core0.c,*/Appl_Core1.c,*/Appl_Core2.c,*/Appl_Core3.c,*/Appl_Core3_QM.c,*/Appl_Core4.c,*/Appl_Etm.c,\ */Appl_HSI_If.c,*/Appl_Rtm.c,*/Appl_SleepWakeup_If.c,*/ApplCan_RxSigProcess.c,*/Aptiv_CdcClient_Wrapper.c,*/Aptiv_CDD_TimeSync.c,\ */Aptiv_Client_SWC.c,*/Aptiv_Comm_Mgr.c,*/Aptiv_Diag_Supplier_Notify.c,*/Aptiv_DiagMgr.c,*/Aptiv_Dlog_HweTable.c,\ */Aptiv_E2E.c,*/Aptiv_Error_Manager.c,*/Aptiv_Eth_E2E_Msg_GW_PCAN.c,*/Aptiv_ETS_SWC.c,*/aptiv_f360_oal_adaptation_wrapper.cpp,\ */Aptiv_Fas_Can_Timeout.c,*/Aptiv_Fascan_E2E_Gw_Msg_Read.c,*/Aptiv_IPsec_SWC.c,*/Aptiv_lbist_ram.c,*/Aptiv_MCAL.c,*/Aptiv_Pcan_Timeout.c,\ */Aptiv_Safety_Manager.c,*/Aptiv_SafetyCoding.c,*/Aptiv_Security_Mgr.c,*/Aptiv_Server_SWC.c,*/Aptiv_SleepWakeup.c,*/Aptiv_SleepWakeup_Eth.c,\ */Aptiv_SMU.c,*/aptiv_tracker_out_to_vru_input.c,*/Aptiv_Wdg_Manager.c,*/aptiv_wrapper_vru.cpp,*/Aptiv_XCP_SWC.c,*/aptive_wrapper_vru_fusion.cpp,\ */Blu_HardwareAdapter.c,*/Blu_UserAdapter.c,*/CED_statemachine.c,*/Collect_PCAN_Data.cpp,*/core_timing_log.c,*/Core_Wrapper_F360Tracker.cpp,\ */Cpu_Load.c,*/CTA_statemachine.c,*/Dlog_SweTable.c,*/f360_tracker_globals.cpp,*/f360_tracker_main.cpp,*/Fault_Manager.c,*/fixmac.c,\ */freespace_statemachine.c,*/Internal_Faults.c,*/LCDA_statemachine.c,*/main.c,*/MainWrapper.c,*/Os_Callout_Stubs.c,*/Prog_CryptoAdapter.c,\ */Prog_UserAdapter.c,*/qualifiers.c,*/RECW_statemachine.c,*/scw_statemachine.c,*/Startup_Safety.c,*/TA_statemachine.c,*/TrackerOutToFF.c,\ */UDP_CAL_Logging_Buffer.c,*/UDP_FFOut_Logging_Buffer.c,*/UDP_logging_data.c,*/UDP_TrackerIAL_Logging_Buffer.c,\ */UDP_TrackerInternal_Loggng_Buffer.c,*/UDP_TrackerOAL_Logging_Buffer.c,*/UDP_VRU_ML_Logging_Buffer.c,*/VTC_Manager.c,\ */Wrapper_F360Tracker.cpp,*/Wrapper_F360Tracker_IAL_Ping.cpp,*/Wrapper_F360Tracker_IAL_Pong.cpp,*/Wrapper_F360Tracker_IAL_Pong_Backup.cpp,\ */Wrapper_F360Tracker_OAL_Ping.cpp,*/Wrapper_F360Tracker_OAL_Pong.cpp,*/Wrapper_FF.c,\ */app_iface.h,*/Appl_Core0.h,*/Appl_Core3.h,*/Appl_HSI_If.h,*/Appl_Rtm.h,*/Appl_SleepWakeup_If.h,*/ApplCan_RxSigProcess.h,\ */Aptiv_CDD_TimeSync.h,*/Aptiv_Client_SWC.h,*/Aptiv_Comm_Mgr.h,*/Aptiv_Diag_Supplier_Notify.h,*/Aptiv_DiagMgr.h,*/Aptiv_Dlog_HweTable.h,\ */Aptiv_E2E.h,*/Aptiv_Error_Manager.h,*/Aptiv_MCAL.h,*/Aptiv_Safety_Manager.h,*/Aptiv_SafetyCoding.h,*/Aptiv_Security_Mgr.h,\ */Aptiv_SleepWakeup.h,*/Aptiv_SleepWakeup_Eth.h,*/Aptiv_SMU.h,*/aptiv_vru_ial.h,*/Aptiv_Xcp.h,*/Blu_HardwareAdapter.h,*/Blu_UserAdapter.h,\ */CED_statemachine.h,*/Collect_PCAN_Data.h,*/core_timing_log.h,*/Cpu_Load.h,*/CTA_statemachine.h,*/f360_tracker_globals.h,*/f360_tracker_IAL.h,\ */FaultManager.h,*/FeatureFunction_IAL.h,*/FeatureFunction_OAL.h,*/freespace_statemachine.h,*/Internal_Faults.h,*/LCDA_statemachine.h,\ */macros.h,*/Prog_CryptoAdapter.h,*/Prog_UserAdapter.h,*/qualifier.h,\ */radar_ecu_internal_CORE1.h,*/radar_ecu_vru_classifier.h,*/RECW_statemachine.h,*/scw_statemachine.h,*/TA_statemachine.h,\ */Tracker_OAL.h,*/TrackerOutToFF.h,*/UDP_CAL_Logging_Buffer.h,*/UDP_FFOut_Logging_Buffer.h,*/UDP_logging_data.h,\ */UDP_TrackerInternal_Loggng_Buffer.h,*/VTC_Manager.h,*/Wrapper_F360Tracker.h,*/Wrapper_FF.h,\ */crc32.c,*/recog_side_radar_field_of_view.c,*/Wrapper_FF.c,*/FF_Statistic_Data.c,*/ac_get_pointer.c,\ */tracker_f360_internal_logging.cpp,*/Output_Conv_Wrapper_F360Tracker.cpp,*/object_list_time_stamp.cpp,\ */McalLib.c,*/Bmhd.c,*/Aptiv_Dlog_HweTable.c,*/Bm_UserAdapter.c,*/Blu_HardwareAdapter.c,*/Blu_UserAdapter.c,\ */Dlog_SweTable,*/DcmFbl_UploadServices,*/Crypto_CertificateManagement,*/Aptiv_HAM.c,*/Aptiv_HAM.h,*/Aptiv_Dlog_HweTable.c,*/Prog_UserAdapter.c,\ */Prog_HardwareAdapter.c,*/Dcm_Prog_Glue.c,*/BswM_Callout_Stubs.c,*/Aptiv_Diag_Supplier_Notify.c,*/Prog_CryptoAdapter.c,\ */CtCDDRtMeas_OS.c,*/CtCDDRtMeas_User.c,*/CtCDDRtMeas_OS.h,*/CtCDDRtMeas_User.h',\ messagesPattern: '', unHealthy: '' But I can't give the filename similar in the new one since I getting as I understand it will accept only regular expressions but I can't give the filenames in that way. I also have no knowledge of regular expression I asked my colleague for help but he wasn't able to give a regular expression for the filenames. Please provide if exists any other way to give filenames or an example of how I can give regular expressions for these file names

          Ulli Hafner added a comment -

          Your approach does not really make sense. Don't you have a pattern in the filenames that have all files in common that you want to include? (Or that you want to exclude?)

          A simple regexp of your cumbersome approach would be:

          (.*/file1.c|.*/file2.c|.*/file3.c)
          

          Why do you want to exclude files anyway?

          Ulli Hafner added a comment - Your approach does not really make sense. Don't you have a pattern in the filenames that have all files in common that you want to include? (Or that you want to exclude?) A simple regexp of your cumbersome approach would be: (.*/file1.c|.*/file2.c|.*/file3.c) Why do you want to exclude files anyway?

          krishna added a comment -

          Actually, in my repo, only a few files are developed by my team.

          We want to concentrate more on our files so we want to run a separate analysis concentrating our files

          I will try the suggested pattern as below and update

          (*/app_iface.c|*/app_iface_QM.c|*/Appl_Core0.c)
          

           

          krishna added a comment - Actually, in my repo, only a few files are developed by my team. We want to concentrate more on our files so we want to run a separate analysis concentrating our files I will try the suggested pattern as below and update (*/app_iface.c|*/app_iface_QM.c|*/Appl_Core0.c)  

          Ulli Hafner added a comment -

          A regular expression is no rocket science: https://regex101.com
          Should be a feasible task for someone programming in C.

          Your expression will produce an error because you cannot use * without something before it, see my example.

          Ulli Hafner added a comment - A regular expression is no rocket science: https://regex101.com Should be a feasible task for someone programming in C. Your expression will produce an error because you cannot use * without something before it, see my example.

          krishna added a comment -

          Thanks for the reference I created a regex to my set of files using the link but when I applies I got an error in the groovy script

          recordIssues filters: [excludeFile('.*/Swc_\w+.c')], tools: [taskingVx()]
          


          Can you please any bypass for this

          krishna added a comment - Thanks for the reference I created a regex to my set of files using the link but when I applies I got an error in the groovy script recordIssues filters: [excludeFile( '.*/Swc_\w+.c' )], tools: [taskingVx()] Can you please any bypass for this

          Ulli Hafner added a comment - - edited

          In Groovy you need to escape the backslash, so use

          '.*/Swc_\\w+.c'
          

          Ulli Hafner added a comment - - edited In Groovy you need to escape the backslash, so use '.*/Swc_\\w+.c'

          krishna added a comment - - edited

          Yes it's worked
          I used exclude also and it's working
          Thanks for the help

          krishna added a comment - - edited Yes it's worked I used exclude also and it's working Thanks for the help

          krishna added a comment -

          Hi drulli,

          Is there a way to see only new, fixed, or outstanding warnings data in table

          krishna added a comment - Hi drulli , Is there a way to see only new, fixed, or outstanding warnings data in table

          Ulli Hafner added a comment -

          It would make sense to look at the generated pipeline description and add a help text for all missing properties. (The help text is already available as JavaDoc or in the UI.)

          Ulli Hafner added a comment - It would make sense to look at the generated pipeline description and add a help text for all missing properties. (The help text is already available as JavaDoc or in the UI.)

            drulli Ulli Hafner
            krishna_1997 krishna
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: