|
||||||||
|
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.
I think the way around this is to not define the Mercurial location in the installation itself, but as a node property, so that the actual path varies according to what computer is running the command. Have not prototyped that to confirm it but IIRC this should work.
The better solution in the longer term is to add automatic installers that download well-known ports according to local platform (OS/arch/etc.). This is mainly hampered by the complexity of interaction with Python ports and native extensions. I have not looked recently at whether Jython has matured to the point where it can (efficiently) run Mercurial, which would be by the far the most convenient option.