Hi @joncanning,
Yes, you would need to use git log with the right commit given by the BITBUCKET_COMMIT variable.
The command would something like:
git log --format=%B -n 1 $BITBUCKET_COMMIT
Example of a pipeline that creates a variable with the commit message:
pipelines:
default:
- step:
script:
- COMMIT_MESSAGE=`git log --format=%B -n 1 $BITBUCKET_COMMIT`
- echo $COMMIT_MESSAGE
I hope that helps.
It's workaround - bitbucket CI should predefine the commit message in one of the variables every CI. (like other ci's do, github/gitlab)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.