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

workflow plugin does not provide console to warnings plugin, sleep required

    XMLWordPrintable

Details

    • Bug
    • Status: Fixed but Unreleased (View Workflow)
    • Major
    • Resolution: Fixed
    • warnings-ng-plugin
    • workflow-plugin 1.12
      warnings plugin 4.51
      jenkins 1.641

    Description

      I came up with the following workflow script brooken.groovy, which
      compiles a file with clang, and then invokes the warnings plugin.

      In the console log, there are warnings, but the warnings plugin detects zero warnings.

      I modified the script slightly (fixed.groovy) by inserting a sleep statement before calling the warnings plugin. I re-ran the script and the warnings plugin detected the warnings.

      It looks like the workflow-plugin is not providing the console to the warnings plugin when it needs it? Maybe a flush is missing?

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42642 Warnings reported intermittently

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          relates to

          Task - A task that needs to be done. JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-55215 Log from cmake/ctest steps isn't fully captured on OsX

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          links to

          Web Link PR #1368

          Activity

            Ascending order - Click to sort in descending order
            View 16 older comments
            jglick Jesse Glick added a comment -

            I would still suggest a block-scoped step, though:

            recordingIssues(tools: [javaDoc()]) {
    sh 'mvn -B -ntp -Dmaven.test.failure.ignore verify'
}
            jglick Jesse Glick added a comment - I would still suggest a block-scoped step, though: recordingIssues(tools: [javaDoc()]) { sh 'mvn -B -ntp -Dmaven.test.failure.ignore verify' }
            drulli Ulli Hafner added a comment -

            Yes, of course. I started an implementation in the last year Hacktoberfest but never managed to finish it. Too many other open issues.

            drulli Ulli Hafner added a comment - Yes, of course. I started an implementation in the last year Hacktoberfest but never managed to finish it. Too many other open issues.
            timja Tim Jacomb added a comment -

            drulli the work around may not be needed anymore after workflow-job 2.41? see https://github.com/jenkinsci/workflow-job-plugin/pull/184

            timja Tim Jacomb added a comment - drulli the work around may not be needed anymore after workflow-job 2.41? see https://github.com/jenkinsci/workflow-job-plugin/pull/184
            drulli Ulli Hafner added a comment -

            Ah thanks! Yes, that means I can remove my 5 sec sleep

            drulli Ulli Hafner added a comment - Ah thanks! Yes, that means I can remove my 5 sec sleep
            drulli Ulli Hafner added a comment -

            I'm reopening so that I do not forget to remove the workaround in the warnings plugin.

            drulli Ulli Hafner added a comment - I'm reopening so that I do not forget to remove the workaround in the warnings plugin.

            People

              drulli Ulli Hafner
              rodrigc Craig Rodrigues
              Votes:
              5 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: