-
Bug
-
Resolution: Duplicate
-
Major
-
None
I get "The system cannot find the batch label specified" error even though label exists.
The problems doesn't reproduce when I copy "Execute Windows batch command" text into .bat file and run it.
I've discovered that line endings are NOT CRLF in the batch script stored in config.xml - but they should be.
See http://stackoverflow.com/questions/232651/why-the-system-cannot-find-the-batch-label-specified-is-thrown-even-if-label-ex for explanation.
- duplicates
-
JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type "Execute Windows batch command"
-
- Resolved
-
A better solution would be to modify the Win batch step so that it always generates .bat files with CRLF EOLs, regardless of what EOLs are used when the .bat content is stored in config.xml. See more details in issue 7478, which is duplicated by this one.
Jenkins already has enough problems when parsing XML files containing newlines in element text and it would be pretty complicated to handle config.xml files containing a mix of LF and CRLF EOLs, especially for those who already have automation steps in place to automatically get/modify/generate new jobs.