[
https://issues.jenkins-ci.org/browse/JENKINS-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161696#comment-161696
]
Ken Morse commented on JENKINS-11991:
-------------------------------------
We're seeing this happen too with 1.38; our build tags itself but that now
seems to cause an infinite loop of building. Maybe versions prior to 1.38
ignored the .hgtags file?
> Polling shows changes after job commits and pushes changes
> ----------------------------------------------------------
>
> Key: JENKINS-11991
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11991
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Reporter: Jarek Potiuk
> Assignee: Kohsuke Kawaguchi
>
> As of latest version of mercurial plugin (1.38) the behaviour of the plugin
> changed. We used to make some manuals release jobs to commit some changes
> (increase build number and set a tag) and push it to the origin repo. It
> seems that now every time after release job is executed (and commit and push
> happen), the plugin detects that the repo has changed and triggers another
> build. It was not working like that before...
> Some outputs:
> 1st job (release job run manually):
> 21:25:04 [workspace] $ hg showconfig paths.default
> 21:25:04 [workspace] $ hg pull --rev 1_0
> 21:25:04 [workspace] $ hg update --clean --rev 1_0
> 21:25:04 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> 21:25:04 [workspace] $ hg log --rev . --template {node}
> 21:25:05 [workspace] $ hg log --rev cc3b37d8df1298eabedfad328cbd4a068e27abf8
> 21:25:05 [workspace] $ hg log --template "<changeset node='{node}'
> author='{author|xmlescape}' rev='{rev}'
> date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n"
> --rev 1_0:0 --follow --prune cc3b37d8df1298eabedfad328cbd4a068e27abf8
> Inside the job:
> hg commit -m "Incrementing application version to 1.0-TEST (345" -u
> [email protected] AndroidManifest.xml
> hg tag -f Release_1.0-TEST_345 -u [email protected]
> hg push
> Then polling triggers another job:
> 21:27:04 Started by an SCM change
> 21:27:04 Building on master
> 21:27:04 [workspace] $ hg showconfig paths.default
> 21:27:04 [workspace] $ hg pull --rev 1_0
> 21:27:04 [workspace] $ hg update --clean --rev 1_0
> 21:27:04 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> 21:27:04 [workspace] $ hg log --rev . --template {node}
> 21:27:05 [workspace] $ hg log --rev cc3b37d8df1298eabedfad328cbd4a068e27abf8
> 21:27:05 [workspace] $ hg log --template "<changeset node='{node}'
> author='{author|xmlescape}' rev='{rev}'
> date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n"
> --rev 1_0:0 --follow --prune cc3b37d8df1298eabedfad328cbd4a068e27abf8
--
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
