You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Francis Chuang (JIRA)" <ji...@apache.org> on 2019/01/06 22:32:00 UTC
[jira] [Commented] (CALCITE-2579) Replace moby with another
live-reload solution
[ https://issues.apache.org/jira/browse/CALCITE-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735358#comment-16735358 ]
Francis Chuang commented on CALCITE-2579:
-----------------------------------------
[Witch|https://github.com/unchartedsoftware/witch] appears to address all the shortcomings of watcher and reflex. This will be used for watching the source files and reloading tests during development.
> Replace moby with another live-reload solution
> ----------------------------------------------
>
> Key: CALCITE-2579
> URL: https://issues.apache.org/jira/browse/CALCITE-2579
> Project: Calcite
> Issue Type: Task
> Components: avatica-go
> Reporter: Francis Chuang
> Assignee: Francis Chuang
> Priority: Major
> Fix For: avatica-go-4.0.0
>
>
> moby.yml is used by an internal tool (moby) used to run tests while developing the avatica-go library. It reloads the code in a docker container and executes tests.
> -[Skaffold |https://github.com/GoogleContainerTools/skaffold] is maintained by Google and achieves the same thing. Initial testing has shown that it works pretty well and most of the issues I encountered a few months ago were all resolved.-
> Skaffold requires a kubernetes cluster. Kubernetes can be quite heavy (even when running in single node mode). The current plan is to use [watcher|https://github.com/radovskyb/watcher] and docker-compose. Watcher has some flaws:
> * File change events are processed sequentially (when saving/changing multiple files in one go).
> * We need to wait for the previous test run to complete before it will start the next run (if a file changes while tests are running).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)