# Support scanning of console log with parallel steps

XMLWordPrintable

#### Details

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s:
• Labels:
None
• Similar Issues:

#### Description

If a pipeline contains parallel stages, then the console log will contain an unordered mix of stdout of all parallel stages. This makes it impossible to decided which log message is from which parallel stage. Especially if the step is using make then the log will contain the information messages about the current directory in any order: so file names will be not resolved because of assigning the wrong path.

Workaround so far: cat the console log of each step into a file and parse the file instead.

#### Activity

Hide
Ulli Hafner added a comment -
Show
Ulli Hafner added a comment - Reference: https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1F11wKsJtfsUWy4h3ErgvxmyM4BQVrY-gGNZtb9WwgQg%40mail.gmail.com
Hide
James Whitworth added a comment - - edited

Has there been any progress on this issue?

I've hit a problem with the log output from parallel steps being interleaved in such a way that it causes the recordIssues step with the pyLint module to fail to find a file occasionally:

[python_3.8.x_x64] path\to\module************* Module path.to.different_module
path\to\different_module.path.to.different_module:301: [W0511(fixme), ] todo: find the existing tests for fixture tear down.
-----------------------------------
Your code has been rated at 9.99/10
[python_2.7.x_x86] .py:path.to.module:177: [W0105(pointless-string-statement), generate_trial] String statement has no effect


The module path for the python_2.7.x_x86 parallel stage has been split across multiple lines which causes warnings-ng to look for a file called .py instead of path\to\module.py for the pointless-string-statement warning.

I can't easily redirect the output to a file and parse that as pylint doesn't have an output file option, we run the job on Linux and Windows so there is no common syntax for piping the output and the sh and bat steps do not support returning the exit code and the standard output of a command.

Show
James Whitworth added a comment - - edited Has there been any progress on this issue? I've hit a problem with the log output from parallel steps being interleaved in such a way that it causes the recordIssues  step with the pyLint  module to fail to find a file occasionally:   [python_3.8.x_x64] path\to\module************* Module path.to.different_module path\to\different_module.path.to.different_module:301: [W0511(fixme), ] todo: find the existing tests for fixture tear down. ----------------------------------- Your code has been rated at 9.99/10 [python_2.7.x_x86] .py:path.to.module:177: [W0105(pointless-string-statement), generate_trial] String statement has no effect The module path for the python_2.7.x_x86 parallel stage has been split across multiple lines which causes warnings-ng to look for a file called .py  instead of path\to\module.py for the pointless-string-statement  warning. I can't easily redirect the output to a file and parse that as pylint doesn't have an output file option, we run the job on Linux and Windows so there is no common syntax for piping the output and the sh  and bat  steps do not support returning the exit code and the standard output of a command.
Hide
Ulli Hafner added a comment -

Has there been any progress on this issue?

No. See JENKINS-44450 and the corresponding stalled PR.

Show
Ulli Hafner added a comment - Has there been any progress on this issue? No. See JENKINS-44450 and the corresponding stalled PR.

#### People

Assignee:
Ulli Hafner
Reporter:
Ulli Hafner
Votes:
11 Vote for this issue
Watchers:
13 Start watching this issue

#### Dates

Created:
Updated: