There is some situations where this is not desirable : docker_test.sh replaces all .picasoft.net with .test.picasoft.net to help testing. If, for example, you have a mounted config.json with a modified URL, and that you reset the repository, the file will be reset inside the container, leading to strange bug, such as the test container trying to connect to the production database. Also, it is really easier to debug the test instance with test values

[docker_test.sh] Manage special condition where folder is present before pulling but not secret files

More seriously, this step was useful once upon a time because it also used to build the base image for each commit. Now that we have pica-ci-base, this step was only useful to determine what folder have been modified and export some environement variable in a cached file. But Gitlab has race conditions with cache and it will randomly fail, annoying the users of the CI. We will execute the script to set these environment variables at each step of the CI, with a really minimal overhead.