You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/11/02 19:13:00 UTC
[jira] [Updated] (IMPALA-5148) Jenkins runs do not support
coordinated changes in Impala and Impala-Lzo.
[ https://issues.apache.org/jira/browse/IMPALA-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-5148:
----------------------------------
Issue Type: Improvement (was: Bug)
> Jenkins runs do not support coordinated changes in Impala and Impala-Lzo.
> -------------------------------------------------------------------------
>
> Key: IMPALA-5148
> URL: https://issues.apache.org/jira/browse/IMPALA-5148
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.8.0
> Reporter: Alexander Behm
> Priority: Major
>
> Sometimes we need to make coordinated code changes to Impala and Impala-Lzo at the same time. Most of the time it is not possible to test the Impala and Impala-Lzo changes separately due to API changes that make the code not compile unless both modifications are pulled in at the same time.
> As far as I can tell, there currently is no way to run such changes through GVO or with a private build on jenkins.impala.io. Such changes need to be validated manually which is painful, error prone, and probably does not provide the same coverage as running GVO.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org