-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Tested with a fresh, default install of Jenkins 2.42
A Multibranch Pipeline fails reading a Jenkinsfile if the file is encoded in UTF-8 and includes a BOM (Byte order mark).
The error depends on the content of the file, but often shows as a variant of 'No such DSL method XX found'.
If the BOM is removed, the file works fine.
Hier is a Stacktrace wenn the Groovy file contains a BOM and begins with the groovy file marker (#!groovy)
It seams the the whole file will be parsed without the BOM has been removed before.