Docker-compose allows you to follow logs for all up'd services - something like:
docker-compose logs -f -t >> myDockerCompose.log
For my project's CI, we'd love to emit the compose environment's logs as a build artifact (so we can see why a test might have failed). However, I can't quite figure out a way to robustly do this with dobi.
the ideal case would be to emit the run_the_job.sh output to stdout, and emit the docker-compose logs to a separate stream (or file on disk).
Alternatively, I'd even be fine emitting both to the same stdout - ugly, but it's something.
You can sort of get this by dobi some-compose-job:attaching simultaneously, but it runs up in addition.
Docker-compose allows you to follow logs for all up'd services - something like:
docker-compose logs -f -t >> myDockerCompose.log
For my project's CI, we'd love to emit the compose environment's logs as a build artifact (so we can see why a test might have failed). However, I can't quite figure out a way to robustly do this with dobi.
We basically have the following:
the ideal case would be to emit the
run_the_job.sh
output to stdout, and emit the docker-compose logs to a separate stream (or file on disk). Alternatively, I'd even be fine emitting both to the same stdout - ugly, but it's something.You can sort of get this by
dobi some-compose-job:attach
ing simultaneously, but it runsup
in addition.