The is an edge case that can cause the artifcacts directory to no be
created before the artifacts are copied. The consequence is that it is
possible that a file named after the artifacts directory gets created,
and prevent subsequent builds of the same type from running.
The conditions are:
- The build should be done on a user machine (not on CI)
- The build should run no install target
- There should be a single file artifact copied to the root of the
artifacts directory, and this file should be the first of the artifact
list. This is always the case as the log files are hardcoded first.
- The build should run the build_cmake.sh script
What happens is that the artifacts directory for user builds is located
under the build directory, and this directory gets removed by the call
to `git clean -xffd` from the `build_cmake.sh` script. If no install
target is run, the artifact directory remains inexistant until the
artifact copy routine is called. The destination of the log files being
the root of the artifacts directory, it translates to a copy command
similar to `cp <build_dir>/build.clean.log <build_dir>/artifacts` which
effectively copies the log file to a new file called `artifacts`.