You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Brown (JIRA)" <ji...@apache.org> on 2017/09/22 21:25:00 UTC
[jira] [Resolved] (IMPALA-2000) Jenkins jobs should always archive
all test results and log files.
[ https://issues.apache.org/jira/browse/IMPALA-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Brown resolved IMPALA-2000.
-----------------------------------
Resolution: Not A Bug
Old and pertains to a former time.
> Jenkins jobs should always archive all test results and log files.
> ------------------------------------------------------------------
>
> Key: IMPALA-2000
> URL: https://issues.apache.org/jira/browse/IMPALA-2000
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Affects Versions: Impala 2.3.0
> Reporter: Alexander Behm
> Assignee: Mostafa Mokhtar
> Priority: Critical
> Labels: test-infra
> Attachments: screenshot-1.png
>
>
> Example run:
> http://sandbox.jenkins.cloudera.com/job/impala-CDH5-nightly-data-load/490/
> The job above (and others) does not archive the following useful information:
> - BE test results
> - FE test results
> - cluster_logs
> - others?
> The lack of complete archiving prevents us from triaging and tracking failed runs after the fact.
> The goal is to be able to download the artifacts of a job, for example, to be attached to a JIRA tracking a failed Jenkins run. That way all information is still available in JIRA (or elsewhere) after the Jenkins artifacts have been wiped.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)