launchable record build
with multiple --source
options to denote them.LABEL=PATH
:record build
automatically recognizes Git submodules, so there’s no need to explicitly declare them.d7bf8b7c
(from repo 1) and the currently deployed version of service 2 is c39b86a1
(from repo 2), then the effective version of the software being tested can be thought of as something like:launchable record build
right before running tests — i.e. in the green box in the diagram above.launchable record build
, the CLI actually performs two functions that we can split up to support this use case:launchable record commit --source /PATH/TO/REPO
, which lets you record commits separately in each component's build process, andlaunchable record build
options:--no-commit-collection
which disables commit collection (since you're doing it separately), and--commit REPO=HASH
which lets you 'tag' the build with each repository
(Note: This means that the deployed version of each service needs to be available to the process where you run tests.)