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

Jobs in parallel dont display the variant they are running.

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      workflow-job 2.31

      Description

      This issue manifested itself since October 15th.

      When a build is triggered and it runs on multiple slaves parallely, you normally get an output for each line corresponding to the variant its running. Since a Jenkins update on October 15th, this has not been the case. This is making it harder for us to debug the issues on the variants/slaves, as we don't know on which variant the issue is being manifested.

      NOTE:

      Although unrelated, this issue was manifested together with another bug which doesn't allow an anonymous user to view jobs, even if logged in as a non-admin. Only users with admin privileges are allowed to view the logs. That issue has been found on your backlog. https://issues.jenkins-ci.org/browse/JENKINS-54031

       

        Attachments

        1. earlier.JPG
          35 kB
          sakshi sood
        2. earlier.JPG
          35 kB
          sakshi sood
        3. image-2018-11-06-14-35-41-221.png
          16 kB
          fisnik hajredini
        4. image-2018-11-06-14-39-16-393.png
          15 kB
          fisnik hajredini
        5. image-2018-11-08-15-38-49-986.png
          131 kB
          fisnik hajredini
        6. image-2018-11-08-15-39-26-889.png
          19 kB
          fisnik hajredini
        7. image-2018-11-08-15-41-10-158.png
          14 kB
          fisnik hajredini
        8. image-2018-11-20-16-58-04-034.png
          17 kB
          fisnik hajredini
        9. image-2018-11-20-17-20-19-040.png
          169 kB
          fisnik hajredini
        10. JENKINS-54304.png
          234 kB
          Devin Nusbaum
        11. jenkins-browser-log
          13 kB
          fisnik hajredini
        12. log
          4.93 MB
          fisnik hajredini
        13. log-index
          76 kB
          fisnik hajredini
        14. NewNodeConsoleNote-script.js
          4 kB
          fisnik hajredini
        15. now.JPG
          18 kB
          sakshi sood
        16. now.JPG
          18 kB
          sakshi sood
        17. now.JPG
          18 kB
          sakshi sood
        18. Selection_047.png
          157 kB
          fisnik hajredini
        19. Selection_048.png
          196 kB
          fisnik hajredini
        20. two-variants.png
          271 kB
          fisnik hajredini

          Issue Links

            Activity

            Hide
            abubadabu Timm Drevensek added a comment - - edited

            Hey Jesse Glick,

            the change done here has killed our complete option to forward the log data to an external instance! This is really a major change that should be undone! Who cares about the log to be shown within the UI if you operate Jenkins within a corporation where you have some hundert jenkins jobs - you simply don't scroll trough the jobs anymore - you have to have some external processing.

            Before this change we where able to forward all logs to an external FileBeat, split the logs via Logstash and process it within ElasticSearch. With this change, we are limited to the Jenkins UI.

            With this change, there is currently NO efficient way to forward the logs anymore! The only way is the logstash plugin - but here you have to adapt all jobs and don't have any global "forward everything" option anymore (if you rely on 100% pipeline jobs).

            Please re-add the [pipeline step name] and also remove the binary encoded stuff (8mha:////) from the logs.

            Show
            abubadabu Timm Drevensek added a comment - - edited Hey Jesse Glick , the change done here has killed our complete option to forward the log data to an external instance! This is really a major change that should be undone! Who cares about the log to be shown within the UI if you operate Jenkins within a corporation where you have some hundert jenkins jobs - you simply don't scroll trough the jobs anymore - you have to have some external processing. Before this change we where able to forward all logs to an external FileBeat, split the logs via Logstash and process it within ElasticSearch. With this change, we are limited to the Jenkins UI. With this change, there is currently NO efficient way to forward the logs anymore! The only way is the logstash plugin - but here you have to adapt all jobs and don't have any global "forward everything" option anymore (if you rely on 100% pipeline jobs). Please re-add the [pipeline step name] and also remove the binary encoded stuff (8mha:////) from the logs.
            Hide
            jglick Jesse Glick added a comment -

            Timm Drevensek please see linked issues and do not reopen.

            Show
            jglick Jesse Glick added a comment - Timm Drevensek please see linked issues and do not reopen.
            Hide
            tuttul Shah Chowdhury added a comment -

            We ended up reverting back to the old (2.25) level.

            Branch Names in the Raw Logs is critical for us. We have various tools/log-formatters that parse through raw logs. Please put this back. 

            Show
            tuttul Shah Chowdhury added a comment - We ended up reverting back to the old (2.25) level. Branch Names in the Raw Logs is critical for us. We have various tools/log-formatters that parse through raw logs. Please put this back. 
            Hide
            jglick Jesse Glick added a comment -

            Shah Chowdhury as above.

            Show
            jglick Jesse Glick added a comment - Shah Chowdhury as above.
            Hide
            gdemengin Guillaume DeMengin added a comment -

            this issue might be fixed in the GUI ...
            but it still exists for 2 uses cases in which variant information is not available anymore and makes some parts of the logs unusable:

            • when logs are accessed programmatically (using currentBuild.rawBuild.log for example)
            • when logs are accessed through the /consoleText link (to import the logs in a log gatherer for example)

            for those 2 uses cases this workaround might help: https://github.com/gdemengin/pipeline-logparser
            (implementation of https://stackoverflow.com/a/57351397/8380249)

            Show
            gdemengin Guillaume DeMengin added a comment - this issue might be fixed in the GUI ... but it still exists for 2 uses cases in which variant information is not available anymore and makes some parts of the logs unusable: when logs are accessed programmatically (using currentBuild.rawBuild.log for example) when logs are accessed through the /consoleText link (to import the logs in a log gatherer for example) for those 2 uses cases this workaround might help: https://github.com/gdemengin/pipeline-logparser (implementation of https://stackoverflow.com/a/57351397/8380249 )

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              fhajredini fisnik hajredini
              Votes:
              1 Vote for this issue
              Watchers:
              17 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: