GitLab

See #3431.

We want to regularly run all our tests (and not to rely only on branch names).

On demand for the development always when releasing.

- Automatically test for releases
- Manually test whenever we want

we now do this in the test launcher script

so we can use sed to edit it when executing functional tests in docker
with gitlab-ci

See #3310.

1. missing semi-colon
2. Needed `-T` to the `ln` command so that the link is
   not done inside the `next` directory

Requires the environment variable COMPILERS to be defined

Test unit+should+valgrind: unit+should+shouldvdj took almost 3h.

Fix #3310 see vdj#450 for compiler installations on the slave.

We use this for reorganizing where tests are launched

Since in gitlab-ci we are launching the unit tests on the host, and the
database initialisation needs to be launched on the docker container, we
want to separate the two.

starting it in the background doesn't seem to be working. The detached
mode must exist for this purpose

due to our runner meccano having the i686 architecture, for which there
is no official image for MySQL, and alternatives were causing issues.

since we're running docker-compose in the background, we need to wait
for our containers to have started before attempting to run our tests

hopefully this will resolve the syntax error

Since we are building the image in gitlab ci, we should not attempt to
build it in docker-compose. We should also match the build tag to the
docker-compose file.

fix issue with bash syntax for launching docker-compose in the
background.

$CI_COMMIT_REF_NAME should be the correct name for the branch we want to
clone into.

The server functional test failsafe to ensure the docker compose
environment is shut down when the tests fail also needs to return false
in order to ensure the job is marked as failed as expected.

start docker environment with docker compose and launch functional tests

See #2881

allows the use of the 'build_env' build arg which will build the docker
image in "test" mode.
This has two consequences. The first is that all ocnfigurations files
are set to run the env over HTTP for ease of use. The second is the
installation of the necessary packages and programs required to run
watir functional tests in headless mode.

See #2881

Adds a ci job for building and testing a docker image and a job for
deploying a docker image
See #2881