Missing Merge Commit From GitHub In ChangeSet

21 views
Skip to first unread message

Mark Bretl

unread,
Mar 3, 2020, 3:20:53 PM3/3/20
to Jenkins Users
Environment:
Jenkins 2.204.2
github-branch-source 2.6.0
bitbucket-branch-source 2.7.0
git 4.2.0
atlassian-jira-software-cloud 1.0.4

Hello,

I am using Jenkins pipelines and trying to get all commits (and their messages) in a particular build to link to JIRA. I noticed notifications were missing in Jira when the reference to the ticket was in a merge commit in GitHub. This got me to see why the integration was failing. When looking at the ChangeSet log from the currentBuild, if the commit is a merge, then it does not show in the ChangeSets (hudson.plugins.git.GitChangeSet) item list. I searched the Jenkins JIRA server and found the following ticket, https://issues.jenkins-ci.org/browse/JENKINS-49703.

I do also have an on-premise Bitbucket Server 6.9.1 and was able to verify merge commits were being added to the ChangeSet when using the bitbucket-branch-source plugin, so this feels like a limitation on the GitHub side. If merge commits from GitHub repositories are not able to be in ChangeSet logs, I am not able to have developers use the 'squash and merge' functionality for a PR.

Has anyone else run into this? Maybe there is a setting I have missed...

Any help is appreciated.

Thanks,

--Mark


Reply all
Reply to author
Forward
0 new messages