Multiple users have reported (ru support chat example) that their CI uses the following process:
One machine builds the service
Only the required artifacts are stored and packed into Docker
Another machine runs the tests
To better support this workflow, we need the ability to prepare such a Docker image (in debug or release build) with a single command.
The files required for tests:
the binary build/SERVICE_NAME
build/runtests-testsuite-SERVICE_NAME
configs
testsuite tests directory
build/venv-testsuite-SERVICE_NAME
while we are at it, let's also pack the binary of gtest tests
All the files currently have to be placed at the paths within the Docker image that are identical to the paths on the build machine, e.g. /path/to/my-service/build-release/my-service should be put at exactly that path within the Docker.
Multiple users have reported (ru support chat example) that their CI uses the following process:
To better support this workflow, we need the ability to prepare such a Docker image (in debug or release build) with a single command.
The files required for tests:
build/SERVICE_NAMEbuild/runtests-testsuite-SERVICE_NAMEbuild/venv-testsuite-SERVICE_NAMEAll the files currently have to be placed at the paths within the Docker image that are identical to the paths on the build machine, e.g.
/path/to/my-service/build-release/my-serviceshould be put at exactly that path within the Docker.