This repository has been archived by the owner on Nov 25, 2020. It is now read-only.
Best strategy for multi-project builds? #53
Comments
rtyley
added a commit
to rtyley/scanamo
that referenced
this issue
Sep 12, 2019
This is useful for multi-project builds that have some subprojects with tests that require LocalDynamoDB, and others that don't - the two subprojects will need different ports to not interfere with each other (not killing each other's LocalDynamoDB process before time). This problem seemed to rear it's head in the Ophan build as we tried to upgrade to sbt 1.3. See also localytics/sbt-dynamodb#53 and the alternative strategy used in Scanamo itself: scanamo#232
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I can see from #16 & #17 that users are using
sbt-dynamodbin multi-project builds, and it looks like the strategy there is to use a different port for each subproject, starting a new instance ofDynamoDBLocalwith each one.I wasn't aware of that strategy, and actually have a multi-project build with two subprojects both using
sbt-dynamodbon the same port - this seemed to work up until we started an upgrade to sbt 1.3, which seems to be running the tests for those two subprojects concurrently (nice and fast!), and unfortunately sometimes failing when the first subproject to finish kills off theDynamoDBLocalprocess before the second project has finished.Although I could adopt the multi-port strategy (Scanamo didn't make this convenient until
v1.0.0-M11with scanamo/scanamo#507), I'd be interested to know if a single-DynamoDBLocal-instance strategy would be possible - which would presumably be more lightweight for the build-server and faster to run. You'd only want theDynamoDBLocalservice to start if a subproject required it, but only kill it as the entire sbt build came to an end?The text was updated successfully, but these errors were encountered: