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

Block scoped usage

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • warnings-ng-plugin
    • None

      Allow warnings to scan just the console output from steps inside a block in pipelines and preferably give it a name and have multiple warnings reports one per name ie

       

      warnings consoleParsers:[[parserName: 'GNU C Compiler 4 (gcc)']], unstableTotalAll: '0', name: 'GCC' {
  sh 'make'
}
warnings consoleParsers:[[parserName: 'Doxygen']], unstableTotalAll: '0', name: 'Doxygen' {
  sh 'make doc'
}

      Currently things like being able to click on a warning to view the source dosn't work in pipelines if your doing parallel steps over multiple hosts (as the workspace paths differ)

          [JENKINS-44450] Block scoped usage

          David van Laatum created issue -
          David van Laatum made changes -
          Description Original: Allow warning to scan just the console output from steps inside a block in pipelines and preferably give it a name and have multiple warnings reports one per name ie

           
          {code:java}
          warnings consoleParsers:[[parserName: 'GNU C Compiler 4 (gcc)']], unstableTotalAll: '0', name: 'GCC' {
            sh 'make'
          }
          warnings consoleParsers:[[parserName: 'Doxygen']], unstableTotalAll: '0', name: 'Doxygen' {
            sh 'make doc'
          }
          {code}
          Currently things like being able to click on a warning to view the source dosn't work in pipelines if your doing parallel steps over multiple hosts (as the workspace paths differ)           		New: Allow warnings to scan just the console output from steps inside a block in pipelines and preferably give it a name and have multiple warnings reports one per name ie

           
          {code:java}
          warnings consoleParsers:[[parserName: 'GNU C Compiler 4 (gcc)']], unstableTotalAll: '0', name: 'GCC' {
            sh 'make'
          }
          warnings consoleParsers:[[parserName: 'Doxygen']], unstableTotalAll: '0', name: 'Doxygen' {
            sh 'make doc'
          }
          {code}
          Currently things like being able to click on a warning to view the source dosn't work in pipelines if your doing parallel steps over multiple hosts (as the workspace paths differ)
          Ulli Hafner made changes -
          Link New: This issue relates to JENKINS-37325 [ JENKINS-37325 ]
          Ulli Hafner made changes -
          Labels New: analysis-core-2.0

          Ulli Hafner added a comment - - edited

          I think the whole plug-in suite needs to be refactored so we can split the processing into several tasks that could be called individually:

          1. Parse a file or sub-set of the console log with a parser: Return value is a set of warnings
          2. Append a set of warnings to an existing set of warnings
          3. Compute the new and fixed warnings
          4. Create an action that shows the results
          5. Change the build status based on the results
          6. Copy conflicting files to the Jenkins master build results

          Ulli Hafner added a comment - - edited I think the whole plug-in suite needs to be refactored so we can split the processing into several tasks that could be called individually: Parse a file or sub-set of the console log with a parser: Return value is a set of warnings Append a set of warnings to an existing set of warnings Compute the new and fixed warnings Create an action that shows the results Change the build status based on the results Copy conflicting files to the Jenkins master build results
          Ulli Hafner made changes -
          Remote Link New: This issue links to "Page (Jenkins Wiki)" [ 17267 ]

          Ulli Hafner added a comment -

          I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page. Can you please read it carefully and comment or change it accordingly?

          Ulli Hafner added a comment - I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page . Can you please read it carefully and comment or change it accordingly?
          Ulli Hafner made changes -
          Labels Original: analysis-core-2.0
          Ulli Hafner made changes -
          Component/s New: warnings-ng-plugin [ 24526 ]
          Component/s Original: warnings-plugin [ 15513 ]
          Ulli Hafner made changes -
          Rank New: Ranked higher

            drulli Ulli Hafner
            davidvanlaatum David van Laatum
            Votes:
            3 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: