[
https://issues.apache.org/jira/browse/NIFI-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943448#comment-15943448
]
ASF GitHub Bot commented on NIFI-3650:
--------------------------------------
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/1625
@apiri I think there might be two tasks here to make sure everything is
copacetic: (1) remove that part of the tree so we don't bother caching
it/downloading it period and (2) removing it before the build just to make sure
it's not there (will need that the first time this runs anyway if we don't
invalidate the cache).
So I think it makes sense to add this but also keep the other.
> Ensure travis-ci won't cache nifi artifacts
> -------------------------------------------
>
> Key: NIFI-3650
> URL: https://issues.apache.org/jira/browse/NIFI-3650
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Andre F de Miranda
> Assignee: Andre F de Miranda
>
> while caching dependencies is a fair way of improving travis-ci build times,
> the existence of cached NiFi artifacts within maven's ~/.m2 directory may
> hide issues caused by incomplete code refactoring that would otherwise be
> triggered had travis-ci been running a truly clean build.
> We should find a way of balancing caching and possible build false negatives.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
