[JIRA] (JENKINS-14138) New git branch has empty changelist

[tsonderga...@java.net (JIRA)]

tsondergaard commented on JENKINS-14138 New git branch has empty changelist I'm seeing a similar problem. I am using the git plugin with a <mergeTarget> configured. It is therefore quite typical for devs to check in temporary branches that git then merges to the <mergeTarget> branch and pushes back to the central repo. As it is now this means that jenkins doesn't send emails in the case of a build failure for such new branches. I've noticed in the console output from builds on new branches that the git-plugin writes No change to record in branch XXX This is written by the git-plugin if it cannot find a previous build. In the case where a job is configured with a mergeTarget I believe that the right solution is either 1. always use <mergeRemote>/<mergeTarget> as the previous ref or 2. Look for a previous build for the branch first and then fall back to <mergeRemote>/<mergeTarget> The names <mergeRemote> and <mergeTarget> are from the config.xml file, where I for example have: <userMergeOptions> <mergeRemote>origin</mergeRemote> <mergeTarget>release/5.0.0</mergeTarget> </userMergeOptions>

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