[
https://issues.jenkins-ci.org/browse/JENKINS-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159228#comment-159228
]
srikanth madarapu commented on JENKINS-12459:
---------------------------------------------
Yes the -no-merges must be optional. Every time we make a merge we are forced
to invoke the build manually. When there are other modules that are depending
on the merged one, they fail to compile unless the merged one was built.
> Does not trigger a build with a branch merge
> --------------------------------------------
>
> Key: JENKINS-12459
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12459
> Project: Jenkins
> Issue Type: Bug
> Components: mercurial
> Environment: Windows 7, Mercurial
> Reporter: samaursa
> Assignee: Kohsuke Kawaguchi
> Labels: plugin
>
> This issue has been raised earlier, but the 'resolution' to that issue was
> not good, or at least, should have been optional.
> I am not sure how people are tackling this issue in general but if I have a
> 'dev' and 'default' branches, the branches mostly accept merges as
> programmers work in different branches then merge them into dev. When the dev
> compiles and is tested, it is merged into default. We absolutely need the
> dev/default to start building as soon as there is a merge.
> This was disabled when someone raised the issue that there were un-necessary
> builds. I'd rather have un-necessary builds telling me 'Successful!' than no
> builds at all.
> At the very least, there should be a compromise. The following command is
> executed every-time the plugin polls the repository:
> $ hg log --style <repository path>\tmp4601530738732108532style --branch dev
> --no-merges --prune
> I would like the option to remove `--no-merges` from it. Please expose this
> so that we can optionally change it. Currently, this is becoming a big issue
> so much so that we may have to switch from Jenkins.
> I would really appreciate resolution of this issue. Thank you.
--
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
