[ 
https://issues.apache.org/jira/browse/BEAM-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332970#comment-16332970
 ] 

Kenneth Knowles commented on BEAM-3265:
---------------------------------------

"You should just rely on the <strictly less information, strictly flakier 
thing> and not expect to be able to see the <full information, completely 
reliable thing>"

It should be obvious that I filed this because the UI did not present enough or 
correct information. There was no actionable thing to do except re-run the 
whole build locally and hope to gain information. Missing or wrong info in the 
UI isn't a surprising or new situation - the build log and outputs are the 
source of truth and Jenkins puts a veneer on top, and the veneer has bugs and 
limitations.

I haven't hit a problem lately, so I will close this and just file another 
thing the next time I get blocked.

> Gradle test output link is inaccessible URL
> -------------------------------------------
>
>                 Key: BEAM-3265
>                 URL: https://issues.apache.org/jira/browse/BEAM-3265
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Major
>
> When tests fail, you can get output like this:
> "There were failing tests. See the report at: 
> file:///home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_GradleBuild/src/sdks/java/io/kinesis/build/reports/tests/test/index.html"
> Of course, those URL is not something where a click will get you there. We 
> should improve the integration here in some way or another. Really, just 
> dumping the failure seems to be as good as any fancy plugin IMO.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to