Build and publish huginn/huginn-test

[mandrews]

If we publish this docker image, then it will be possible to execute commands from within a huginn development/test environment. For example, it should be possible to test and build an external huginn_agent using this docker image:

# docker-compose.yml
version: '2'

services:
  ...
  huginn_gem_build:
    image: huginn/huginn_test
    environment:
      DATABASE_ADAPTER: postgresql
      TEST_DATABASE_NAME: huginn
       ...
    links:
      - postgres
    command: rake prepare spec build
    working_dir: /build
    volumes:
      - .:/build

I don't think the Travis job will work until docker.io/huginn/huginn-test is created:

DOCKER_IMAGE=huginn/huginn-test DOCKERFILE=docker/test/Dockerfile ./build_docker_image.sh

docker pull $DOCKER_IMAGE
Using default tag: latest
Pulling repository docker.io/huginn/huginn-test
Error: image huginn/huginn-test:latest not found

[dsander]

Being about to use the test image for Agent gems looks awesome!

You are right, we first need to push a image to huginn/huginn-test. I think we should change how the image is build. Because the Travis jobs run in parallel the test image would always be based on the previous single-process image.
We could use build stages which would probably clean up the travis config but also slow down the build because stages are run successively. An other option would be to change the build_docker_image.sh script to spawn another build for the test image after the single-process is done. Appending this to the script should do the trick:

if [[ $DOCKER_IMAGE == "huginn/huginn" ]]; then
  DOCKER_IMAGE=huginn/huginn-test DOCKERFILE=docker/test/Dockerfile ./build_docker_image.sh
fi

[mandrews]

@dsander good idea - updated the PR with your suggestion

[dsander]

@mandrews I think I was wrong yesterday. Since the test image is based on huginn/huginn-single-process we should build it after that one, right?

[mandrews]

@dsander good catch - sorry I missed that 👍

[dsander]

Thanks!