Fix MSBuild parser regression with masked **** paths in Jenkins logs

[akash-manna-sky]

Fix MSBuild parser regression with masked **** paths in Jenkins logs

Fixes #1476

Testing done

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[uhafner]

I wonder what happens in Jenkins then? When I have a file C:\***\file.txt then the file is reported as issue, but later on the file cannot be found in the workspace which produces another error.

[akash-manna-sky]

I wonder what happens in Jenkins then? When I have a file C:\***\file.txt then the file is reported as issue, but later on the file cannot be found in the workspace which produces another error.

What should I do?

[uhafner]

Wait for an answer in the issue. I asked the reporter for feedback...

I think your change will restore the old behavior but somehow is not the correct way to handle such files.