Avoid commiting settings.xml file by using Gitlab File Variable
## Description I think the settings.xml file is a good candidate for using [Gitlab-CI File variable](https://docs.gitlab.com/ee/ci/variables/#use-file-type-cicd-variables). Unfortunately it's not well supported by the template, as you can't specify the location of this file, it's hard-coded as `$MAVEN_CFG_DIR/settings.xml`. There is a workaround which is to override `MAVEN_CLI_OPTS` by expanding `-s $MVN_SETTINGS_PATH` to the default value but it's not ideal. `MAVEN_CLI_OPTS: "--no-transfer-progress --batch-mode --errors --fail-at-end --show-version -DinstallAtEnd=true -DdeployAtEnd=true -s $MVN_SETTINGS_PATH"` `MVN_SETTINGS_PATH` being a Gitlab-CI File Variable. Currently, I use this workaround to avoid git commiting the settings.xml in my project. What do you think of this use case ?
issue