-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Ubuntu 10.04 LTS, Jenkins 1.461, Phing Plugin 0.11, Phing 2.4.12
The build log generated by Jenkins is loaded with junk characters where in/around log output coming from Phing.
JENKINS_HOME/jobs/[JOBNAME]/builds/[BUILDNUMBER]/log
Sample output...
At revision 26 looking for '/var/lib/jenkins/jobs/JOBNAME/workspace/build/buildscripts/build.xml' ... use '/var/lib/jenkins/jobs/JOBNAME/workspace' as a working directory. [workspace] $ phing -buildfile /var/lib/jenkins/jobs/JOBNAME/workspace/build/buildscripts/build.xml -logger phing.listener.DefaultLogger Buildfile: /var/lib/jenkins/jobs/JOBNAME/workspace/build/buildscripts/build.xml ^[[8mha:AAAAZB+LCAAAAAAAAABb85aBtbiIQSejNKU4P0+vIKc0PTOvWK8gIzMvXS85P684PydVLwDEC0ksSk8t8csvSe1Zynx/wmzdSUwMDBVFDFJQrTDFzhAapJABAhhBCgsAxIr4amoAAAA=^[[0mname-of-project > clean: ^[[8mha:AAAAZB+LCAAAAAAAAABb85aBtbiIQSejNKU4P0+vIKc0PTOvWK8gIzMvXS85P684PydVLwDEC0ksSk8t8csvSe1Zynx/wmzdSUwMDBVFDFJQrTDFzhAapJABAhhBCgsAxIr4amoAAAA=^[[0mname-of-project > prepare: [mkdir] Created dir: /var/lib/jenkins/jobs/JOBNAME/workspace/artifacts/code-browser [mkdir] Created dir: /var/lib/jenkins/jobs/JOBNAME/workspace/artifacts/logs [mkdir] Created dir: /var/lib/jenkins/jobs/JOBNAME/workspace/artifacts/pdepend [mkdir] Created dir: /var/lib/jenkins/jobs/JOBNAME/workspace/artifacts/phpdox ^[[8mha:AAAAZB+LCAAAAAAAAABb85aBtbiIQSejNKU4P0+vIKc0PTOvWK8gIzMvXS85P684PydVLwDEC0ksSk8t8csvSe1Zynx/wmzdSUwMDBVFDFJQrTDFzhAapJABAhhBCgsAxIr4amoAAAA=^[[0mname-of-project > phplint: ^[[8mha:AAAAZB+LCAAAAAAAAABb85aBtbiIQSejNKU4P0+vIKc0PTOvWK8gIzMvXS85P684PydVLwDEC0ksSk8t8csvSe1Zynx/wmzdSUwMDBVFDFJQrTDFzhAapJABAhhBCgsAxIr4amoAAAA=^[[0mname-of-project > build: ^[[8mha:AAAAZR+LCAAAAAAAAABb85aBtbiIQTejNKU4P0+vIKc0PTOvWK8gIzMvXS85P684PydVLwDE8y8tSc7PTfXLL0k9c6yzJK01gpOJgaGiiEEKqhem2hlCgxQyQAAjSGEBAOPRMRprAAAA^[[0mBUILD FINISHED Total time: 0.1892 seconds Finished: SUCCESS
I have already reviewed similar issue JENKINS-10034. The excess characters are different, and I am using the Phing plugin, not a command line call. Plus you can see that the plugin is using the -logger phing.listener.DefaultLogger argument as expected.
That being said, running the phing command "raw" from the command line does produce coloring output that aligns with the junk output.