Build fails on Jenkins with

37 views
Skip to first unread message

Stefan Eike

unread,
May 23, 2017, 8:59:49 AM5/23/17
to DITA-OT Development

Hi,

I have a job that successfully runs locally, but fails on our Jenkins CI instance. It seems that someone uses a forbidded character, probably this one: http://www.fileformat.info/info/unicode/char/fc/index.htm, somewhere. I cannot find it and I absolutely have no idea how I should debug this any further. Could someone please give me a debugging advice?


/data/var/lib/jenkins/workspace/cargosoft_develop-PA2B6SF577HLVMOA5YVZOYQTN77OJIP75MMNU6A4DRJNSJHHGFOA/dita-ot/plugins/org.dita.base/build_init.xml:61: Fatal error during transformation using /data/var/lib/jenkins/workspace/cargosoft_develop-PA2B6SF577HLVMOA5YVZOYQTN77OJIP75MMNU6A4DRJNSJHHGFOA/dita-ot/xsl/job-helper.xsl: Output character not available in this encoding (decimal 252); SystemID: file:/data/var/lib/jenkins/workspace/cargosoft_develop-PA2B6SF577HLVMOA5YVZOYQTN77OJIP75MMNU6A4DRJNSJHHGFOA/dita-ot/xsl/job-helper.xsl; Line#: 101; Column#: -1

Thank you very much!

Greetings,
Stefan

Stefan Eike

unread,
May 23, 2017, 9:49:45 AM5/23/17
to DITA-OT Development
Hi Radu,

thank you for your suggestion. I tried both <xsl:output method="text" encoding="UTF-8"/> and <xsl:output method="text" encoding="UTF-16"/>, but the build still fails with the same message.

Greetings,
Stefan

Radu Coravu

unread,
May 24, 2017, 2:34:43 AM5/24/17
to Stefan Eike, DITA-OT Development
Hi Stefan,

So the cause for this is probably the fact that you have an umlaut "ü" in a file or a folder path somewhere, then that "ü" gets in the ".job.xml" which should be found in the transformation temporary files folder (so you can search for it there), then the job-helper.xsl tries to process it and probably and fails because it tries to output text files with ASCII encoding. But I cannot reproduce this problem (unless I manually specify encoding='ASCII' in the stylesheet) on my side as Saxon by default uses UTF-8 as the default encoding for writing both text and XML files.

Regards,
Radu

--
You received this message because you are subscribed to the Google Groups "DITA-OT Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Radu Coravu

unread,
May 24, 2017, 2:36:56 AM5/24/17
to Stefan Eike, DITA-OT Development
There are also other problems when using German accented characters in file and folder paths. I added one such problem some time ago:
https://github.com/dita-ot/dita-ot/issues/2476
So you should avoid such characters in the file and folder paths for now.

Regards,
Radu

Stefan Eike

unread,
May 24, 2017, 2:57:49 AM5/24/17
to DITA-OT Development, s.ei...@gmail.com
Hi Radu,

I supposed the same. But there is no file or directory containing any special characters. I'm aware of this problem and we have validators for checking this. The problem only occurs on the Jenkins, the build runs fine on Windows. It is probably some kind of side effect... And I run other projects with the same settings on the same Jenkins instance without any problems...

Regards,
Stefan
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-dev...@googlegroups.com.

Stefan Eike

unread,
May 24, 2017, 3:38:59 AM5/24/17
to DITA-OT Development, s.ei...@gmail.com
Hi,

I have found and fixed the problem. The build failed after processing the file image.list, which is created in the temp dir. This file contains paths to images. In this file, I have found two paths with Umlauts (ü). The files themselves were correctly renamed, but someone missed to fix the (broken) hrefs in the topics. Now the build runs fine.

Thanks again, Radu!

Greetings,
Stefan
Reply all
Reply to author
Forward
0 new messages