|
||||||||
|
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.
The core functionality of the SCM Trigger.poll() does not allow triggers to receive parameters, but the post-commit hooks can receive them.
In the case you describe you pass the the revision Id as the branch, and this is not taken into account during polling as the poll methods cannot use this information.
There are two features here that could be implemented:
1. Pass a named branch via post commit message and then trigger polling only on the jobs that have branch set in their config.
Add additional checks to MercurialStatus Class[1] for branchId.
2. Checkout a particular revision in a triggered job.
Create a Revision Action in the MercurialStatus class [1] that is added to the build when started, if polling triggers it.
that is fetched during the checkout()[2] phase of the SCM process, and sets the workspace to that revision.
Similar to how the Subversion plugin does it.
Removing core and parameterized-trigger components as this is a Mercurial plugin only issue.
[1] https://github.com/jenkinsci/mercurial-plugin/blob/master/src/main/java/hudson/plugins/mercurial/MercurialStatus.java
[2] https://github.com/jenkinsci/mercurial-plugin/blob/master/src/main/java/hudson/plugins/mercurial/MercurialSCM.java#L366