[
https://issues.apache.org/jira/browse/FLINK-22614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341848#comment-17341848
]
Robert Metzger commented on FLINK-22614:
----------------------------------------
Yes, this change makes sense. There's no specific reason, except maybe lack of
time ;)
> Provide build artifacts for YARN e2e tests
> ------------------------------------------
>
> Key: FLINK-22614
> URL: https://issues.apache.org/jira/browse/FLINK-22614
> Project: Flink
> Issue Type: Improvement
> Components: Build System / Azure Pipelines
> Affects Versions: 1.14.0
> Reporter: Matthias
> Priority: Major
> Labels: starter
>
> The YARN e2e don't publish the artifacts if the build failed. Instead, we
> have to rely on the printout of the watchdog process that prints all the
> artifacts' content to stdout. This is tedious when analyzing specific
> artififacts as we have to jump to specific lines in a single log file instead
> of selecting the relevant artifact from the build artifact archive.
> FYI: Anything that's collected in {{debug_copy_and_show_logs}} of
> {{flink-end-to-end-tests/test-scripts/common_yarn_docker.sh}} should be
> included in the build artifacts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
