This is how I try to send the commit message but the pipe gives me an error:
- step:
runs-on: self.hosted
name: Desplegar PRO
deployment: production
trigger: manual
script:
- apt-get update && apt-get install -y git
- COMMIT_MESSAGE=`git log --format=%B -n 1 $BITBUCKET_COMMIT`
- echo $COMMIT_MESSAGE
- git add reports/resultado.txt
- git commit -m "[skip ci] $COMMIT_MESSAGE"
- pipe: atlassian/email-notify:0.4.4
variables:
USERNAME: '***@******'
PASSWORD: $workspaceVarPassword
FROM: '***@*****'
TO: '****@e*******'
HOST: '**********'
PORT: '587'
TLS: 'TRUE'
SUBJECT: 'Informe de Impactos'
BODY_PLAIN: '$COMMIT_MESSAGE'
ATTACHMENTS: 'reports/resultado.txt'Status: Downloaded newer image for bitbucketpipelines/email-notify:0.4.4
✖
Validation errors:BODY_PLAIN:
- must be of string type
I have a similar issue in specific cases, eg when I use the semicolon (:) or hash (#) signs.
I have the next body template:
'Серверное приложение Node Proxy успешно выпущено на ${ENVIRONMENT}. Обновление было запущено коммитом $COMMIT_MESSAGE. Версия приложения ${SERVER_VERSION}.'
And, if I have the next commit message:
fix(app) - do some changes (issue 1235)
The pipe will process successfully.
But, I will receive same error for messages like
fix(app): do some changes (issue 1235)
or
fix(app) - do some changes (#1235)
The problem is, that semicolon is required when the team follow Conventional commits, and hash automatically uses in merge commit, eg:
Merged in feature/map-team-developers-id (pull request #947)
It would be nice if the BODY_PLAIN will accept these symbols.
Hi @Luis ,
Thank you for your question!
It would be nice if you provide us with details about BODY_PLAIN variable context.
Cheers,
Oleksandr Kyrdan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! it is a variable of the pipe https://bitbucket.org/atlassian/email-notify/src/master/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted]
yep,
but provide us with real example of BODY_PLAIN text, please, so we'll try to find a root cause.
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.