[
https://issues.apache.org/jira/browse/BIGTOP-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635272#comment-13635272
]
Sean Mackrory commented on BIGTOP-873:
--------------------------------------
Sorry, Cos - meant to weigh in yesterday but the times I remembered and the
times I had working Internet didn't overlap much :)
+1 to rolling it back as you did - it was indeed meant to fix a stale ivy cache
which was breaking Jenkins builds. That shouldn't normally be a problem, so if
clearing it causes new problems we shouldn't be clearing it. If it happens
again we'll just need to figure out how we clear the Ivy cache manually on the
machines in question.
Thanks for resolving the issue!
> Hive needs Ivy cache cleared
> ----------------------------
>
> Key: BIGTOP-873
> URL: https://issues.apache.org/jira/browse/BIGTOP-873
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Fix For: 0.6.0
>
> Attachments: BIGTOP-873.1.patch, BIGTOP-873.patch
>
>
> Some Hive builds started failing after the upgrade to Hive 0.10.0:
> http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Hive/306/
> I have tried unsuccessfully to reproduce the problem on a couple of the
> affected operating systems - I believe the problem is a stale ivy cache. We
> could try invoking the relevant ant target in do-component-build, or perhaps
> we can just do it manually on each of the affected Jenkins slaves.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
