User is getting an error "tail: cannot open ‘/apps/jenkins/pipeline-worker/workspace/jenkins-
build12/Utilities/CASTHighlightScan/HighlightBatchScan/xxxx/xxxx/HLAutomation.log’ for reading: No such file or directory" while trying to move the current scan process to New Jenkins Environment.
Solution
- Instead of giving the complete path for the workingdir as
/apps/jenkins/pipeline-worker/workspace/jenkins-
build12/Utilities/CASTHighlightScan/HighlightBatchScan/xxxx/xxxx/HLAutomation.log in your build, instead you should just give the path of the directory and it will create the HLAutomation.log inside the workingDir - Check whether the required Perl modules on the machine is installed. See README of the Command Line.
- Try with a recent version of the command line. It is recommended to keep the CLI up to date with recent versions as newer versions will have new fixes, new technologies, new patterns.
Related Articles
Highlight Automated Code Scan (Command Line)
Details
28729
Comments