Hello, We have a project with multiple packages built using stack, that also contains or depends on non-Haskell software. I have written a shake file on top of that to orchestrate building docker images for all our services and running system tests. This shake file contains rules for triggering build of images that depend on source files. The build itself uses stack inside docker containers (not using stack's docker mode but it could be the case...). The dependency graph looks like that
source files ^ ^ | | | +-- service exe <--- service docker image <---+ | +-- tests execution + ----- tester exe <--- tester docker image <---+ The problem I am facing is that changing any source file triggers a full rebuild of the 2 containers, although some of the source files are not relevant to one or the other. I don't know how to solve this issue. I thought of leveraging stack's capabilities to extract a dependency graph and manually check which project to rebuild depending on which source files changed but this seems pretty much redundant. I would appreciate any insight on how best to handle this kind of configuration. Regards, Arnaud Bailly -- You received this message because you are subscribed to the Google Groups "haskell-stack" group. To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stack+unsubscr...@googlegroups.com. To post to this group, send email to haskell-stack@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/39b78d6c-5a07-4e05-a4ab-67fe147a9dc0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
