|
||||||||
|
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/d/optout.
Could be supported. Doing this mostly defeats the purpose of using the Mercurial plugin at all, as opposed to just adding a shell step to run hg clone directly, since changelogs and updates and polling would not work in such a job. I am guessing that what you really want to do is to create a series of jobs sharing mostly the same configuration but using different repository URLs, which is better accomplished with other plugins: Templates (if using Jenkins Enterprise), or Job DSL, etc.