So, we expect build under hash of commit merged in master: 144311b20df08572b13c3b4e20c72796e70e6d5c
But in facts scm step checkout commit from fromRef.lastestCommit (326eabb767f9bd19dfb510a81284142adad595a5)
And env.BITBUCKET_PAYLOAD has no information about properties.mergeCommit (144311b20df08572b13c3b4e20c72796e70e6d5c). So, we can`t checkout expected commit via git command.
Hi,
Our team uses BB-server and pipeline configured to build on PR merge in master
Problem occurs when we use merge strategy "Merge commit --no-ff". Bitbucket sends:
So, we expect build under hash of commit merged in master: 144311b20df08572b13c3b4e20c72796e70e6d5c
But in facts scm step checkout commit from fromRef.lastestCommit (326eabb767f9bd19dfb510a81284142adad595a5)
And env.BITBUCKET_PAYLOAD has no information about properties.mergeCommit (144311b20df08572b13c3b4e20c72796e70e6d5c). So, we can`t checkout expected commit via git command.
Our Jenkins file (if needed):
I`m tried different combinations of trigger and scm step configuration but result is always the same. Can you help?