Hi,
On 10.06.19 01:45, Francis Chuang wrote:
Hey everyone,
I am currently setting up automated website builds for Apache Calcite.
We are currently using docker-compose and the jekyll image to generate
the assets on our machines locally:
https://github.com/apache/calcite/blob/test-site/site/docker-compose.yml
This works well and `docker-compose run ` command returns after the
generation is completed.
A docker-compose run ... or docker run will run not in daemon mode which
means the calling process is blocked until you press ctrl-c ...
The first thing I would suggest to use is:
docker-compose run -d ...
-d => Daemon mode which run all processes in background.
This will not block the whole pipeline from running...
But be aware that your consuming services must be handling that the
starting process may take time to be up and running
correctly...(resilence..)
Kidn regards
Karl Heinz Marbaise
The problem is that when we use `docker-compose run ...` to generate the
assets on Jenkins, it never returns. We are using this Jenkinsfile:
https://github.com/apache/calcite/blob/test-site/Jenkinsfile
The logs showing the generating being successful, but not terminating
and manually aborted are here:
https://builds.apache.org/job/Calcite-Site/9/console
I have tried using the bash and sh interpreters when running
`docker-compose run`, but it does not make any difference.
Does anyone know what might be the cause?
Francis
