History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2325
Type: Bug Bug
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Robin Shen
Reporter: Julian Bassett
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Build agent and encodings issue

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
RHEL 6.4 64Bit (qbserver/vvm780) MacOS 10.10.2 (agent)
System locale set to de_DE.UTF-8 set on both machines

 Description  « Hide

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.

 All   Comments   Work Log   Change History      Sort Order:
Julian Bassett [12/Feb/15 09:54 AM]
The problem wwith javadoc is solved - it was missing an encoding entry
but the commit-step problem remains

Robin Shen [13/Feb/15 01:03 AM]
This issue might not be relevant to QB. When transferring files (either via publish or via step input/output files), QB does not touch file content, it just tar files and untar them at another side. You may compare binary content of the file before/after transferring.

Julian Bassett [13/Feb/15 11:20 AM]
Hi Robin,
thanks for the info. Is it possible for us to see the content of the svn step? We send the command:
  "svn commit -m "set Version für CD build"
to the agent but we see it doesn't arrive correctly at the agent (or is not correctly handled by the agent).

Thanks for your help in advance

Robin Shen [14/Feb/15 12:55 AM]
QB itself does not provide any svn commit command. Maybe you are issuing it in your own build script?

Julian Bassett [18/Feb/15 08:46 AM]
Thanks for the information - please close ticket.

Robin Shen [18/Feb/15 01:51 PM]
Not a QB problem