[ 
https://issues.jenkins-ci.org/browse/JENKINS-13174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163480#comment-163480
 ] 

Ken Morse commented on JENKINS-13174:
-------------------------------------

Perhaps the user should be able to configure which files are ignored by the 
plugin. Alternatively, the build looping problem could also be resolved by 
ignoring any changes from the build machine, rather than ignoring changes to 
particular files.
                
> 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

        

Reply via email to