![](/images/bluepixel.gif)
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 12/Feb/15 09:32 AM
Updated: 18/Feb/15 01:51 PM
|
|
|
Component/s: |
None
|
Affects Version/s: |
5.1.43
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
RHEL 6.4 64Bit (qbserver/vvm780) MacOS 10.10.2 (agent)
System locale set to de_DE.UTF-8 set on both machines
RHEL 6.4 64Bit (qbserver/vvm780) MacOS 10.10.2 (agent)
System locale set to de_DE.UTF-8 set on both machines
|
|
Hello,
we have an issue with a build agent and encodings. The build agent is running under MacOS 10.10.2 and Java 1.7.0_75.
Inside some files we have Umlaute in the comments (special german characters ä,ü,ö,..). The files itself are downloaded correctly by the build agent. If I open them with an text editor I see that every comment is displayed correctly.
In some step we build the javadoc and upload it to our internal repository system. When I look at these javadoc-artefacts the encoding is broken (e.g. it says "Gibt ein Test-Json-String zurück" but should say "Gibt ein Test-Json-String zurück"
In another step we commit to our VCS with a comment that contains Umlaute. There we get the following error message:
"10:07:55,753 ERROR - Step 'master>stage-compile>workspace-check_in_changes' is failed: Failed to run command: svn commit -m "set Version für CD build"
Command return code: 1
Command error output: svn: E000022: Commit failed (details follow):
svn: E000022: Error normalizing log message to internal format
svn: E000022: Can't convert string from native encoding to 'UTF-8':
svn: E000022: set Version f?\195?\188r CD build"
So the Umlaut doesn't seem to be correctly transferred from our quickbuild-mainserver to the build agent.
|
Description
|
Hello,
we have an issue with a build agent and encodings. The build agent is running under MacOS 10.10.2 and Java 1.7.0_75.
Inside some files we have Umlaute in the comments (special german characters ä,ü,ö,..). The files itself are downloaded correctly by the build agent. If I open them with an text editor I see that every comment is displayed correctly.
In some step we build the javadoc and upload it to our internal repository system. When I look at these javadoc-artefacts the encoding is broken (e.g. it says "Gibt ein Test-Json-String zurück" but should say "Gibt ein Test-Json-String zurück"
In another step we commit to our VCS with a comment that contains Umlaute. There we get the following error message:
"10:07:55,753 ERROR - Step 'master>stage-compile>workspace-check_in_changes' is failed: Failed to run command: svn commit -m "set Version für CD build"
Command return code: 1
Command error output: svn: E000022: Commit failed (details follow):
svn: E000022: Error normalizing log message to internal format
svn: E000022: Can't convert string from native encoding to 'UTF-8':
svn: E000022: set Version f?\195?\188r CD build"
So the Umlaut doesn't seem to be correctly transferred from our quickbuild-mainserver to the build agent.
|
Show » |
No work has yet been logged on this issue.
|
|