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

Block scoped usage

    XMLWordPrintable

Details

    Description

      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)

      Attachments

        Issue Links

          Activity

            drulli Ulli Hafner added a comment -

            What do you want to comment? This issue? Then just continue in Jira.
            Or would you like to ask generic questions? Then please use the Gitter channel.

            drulli Ulli Hafner added a comment - What do you want to comment? This issue? Then just continue in Jira. Or would you like to ask generic questions? Then please use the Gitter channel.

            drulli, as the wiki is now read-only, do you accept comments on the requirements via some other channel?

            kon Kalle Niemitalo added a comment - drulli , as the wiki is now read-only, do you accept comments on the requirements via some other channel?
            drulli Ulli Hafner added a comment - - edited I created a proof of concept: https://github.com/jenkinsci/warnings-ng-plugin/pull/235 Seems to need some additional work https://groups.google.com/d/msg/jenkinsci-dev/C3cQQSRWpqI/NJcSDsH9BwAJ . Example implementation of callback: https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/474cea2a53753e1fb9b166fa1ca0f6184b5cee4a/src/main/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepExecution.java#L390
            drulli 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?

            drulli 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?
            drulli 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
            drulli 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

            People

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

              Dates

                Created:
                Updated: