I've added the <localRepository> key to my Maven settings.xml to define a custom local repository based on environment variables:

<localRepository>/build/m2repository-review/${env.GERRIT_BRANCH}-${env.GERRIT_TOPIC}</localRepository>

This is so that I can use an adhoc-pipeline based on which branch/topic is being built from our Gerrit Code Review server.

This works fine, except for when Jenkin's Maven support tries to parse the poms, and uses the local repository defined as-is without parsing any environment variables local to the build job.

So I end up with a directory called "/build/m2repository/develop-${env.GERRIT_TOPIC}" - and no artifacts being resolved.