[
https://issues.jenkins-ci.org/browse/JENKINS-13174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163499#comment-163499
]
John Engelman commented on JENKINS-13174:
-----------------------------------------
@jglick I saw that JIRA ticket for adding sub-repo support and just as an FYI,
we've been using Jenkins with a project that has 3 sub-repositories in it just
fine for the last year. We haven't had any issues with it and I believe the
Mercurial repository sharing and caching works out-of-the box. Not sure what
else would be left to add for support.
Thanks for getting a patch in though so quick. Appreciate it.
> Stop changeset tags from being counted as a change in Mercurial Plugin polling
> ------------------------------------------------------------------------------
>
> Key: JENKINS-13174
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13174
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Affects Versions: current
> Reporter: Neil Kay
> Assignee: jglick
>
> We have the slave build machines polling Mercurial repositories, using the
> Mercurial plugin, to trigger builds.
> During the Jenkins job, we create and push a tag changeset as part of the
> build process.
> This tag changeset is detected by polling and causing an infinite loop of
> builds.
> I've looked into other options, I notice the notice away from polling to be
> more push activated, which sounds good, but it seems this still relies on
> polling to detect what has changed, so it seems this would still be a problem.
> The other thing that sounded like it may help was "modules" in the Mercurial
> plugin, but this is a huge change to move lots of repositories to put
> everything except the hgtags file into a sub folder and then specify that sub
> folder as a module.
> If tag changesets were ignorred by polling, similar to a change that was made
> to ignore merge changesets, all would be good in the world :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
