Change By: talios (31/Jan/14 1:28 AM)
Description: 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
 in  as-is without parsing any environment variables local to  the  main Jenkins configuration  build job .

When set to So I end up with a directory called  " default", Jenkins uses ~ / .m2 build / repository as a hard m2repository/develop - coded value, rather than using what is defined in settings ${env . xml GERRIT_TOPIC}" - and no artifacts being resolved .
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to