-
Bug
-
Resolution: Fixed
-
Major
-
None
When looking at a log that has the timestamper plugin enabled, I see something like this when I click on the line that trigger the build failure analyzer.
[8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtrZTnRAIAA6DkZ+BAAAA[0mmessage : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project project-name: Compilation failure
[JENKINS-15926] Build Failure Analyzer with Timestamper output ugly.
Tomas Westling
added a comment - Do you have any other plugin which annotates the log in any way? The lines above are not from the Build Failure Analyzer but from the timestamper plugin. Normally the log is annotated before shown by the timestamper but we have our own implementation for showing the log which causes these lines to appear.
We have a change ready that should fix these problems by using an annotator in the Build Failure Analyzer as well.
Tomas Westling
added a comment - Do you have any other plugin which annotates the log in any way? The lines above are not from the Build Failure Analyzer but from the timestamper plugin. Normally the log is annotated before shown by the timestamper but we have our own implementation for showing the log which causes these lines to appear.
We have a change ready that should fix these problems by using an annotator in the Build Failure Analyzer as well. Tomas Westling
added a comment - Fixed in Build Failure Analyzer 1.3.0 
Alexander Artemov
added a comment - I have 1.3.0 version, but the problem is still actual. I can see in my log something like:
[8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtpm64sNhAAbQyiWBAAAA[0mStarted by user [8mha:AAAAmh+LCAAAAAAAAABb85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzBEgY+/dLi1CL9xMSiktTc/DIAGVLEucMAAAA=
Alexander Artemov
added a comment - I have 1.3.0 version, but the problem is still actual. I can see in my log something like:
[8mha:AAAAdB+LCAAAAAAAAABb85aBtbiIQSOjNKU4P0+vIKc0PTOvWK8kMze1uCQxtyC1SC8ExvbLL0llgABGJgZGLwaB3MycnMzi4My85FTXgvzkjIoiBimoScn5ecX5Oal6zhAaVS9DRQGQtpm64sNhAAbQyiWBAAAA[0mStarted by user [8mha:AAAAmh+LCAAAAAAAAABb85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzBEgY+/dLi1CL9xMSiktTc/DIAGVLEucMAAAA= I have the same issue with 1.3.0 version and 1.5.2 of timestamper plugin.
23:02:18 [BFA] Scanning build for known causes...
23:02:18
23:02:18 [BFA] Done. 0s
23:02:18 Finished: FAILURE
Started by user [8mha:AAAAnB+LCAAAAAAAAABb85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE
...
Tomas Westling
added a comment - Fixed in fd6d360840afec3cae00b1ded8f7b84b9fcdc295 Tomas Westling
added a comment - Released in 1.4.0 
We are not using the timestamper plugin, but also get such output in our build logs. It looks like these lines are randomly added, because they are not just added to failure lines.