Consider setting APPVEYOR_REPO_COMMIT_MESSAGE_EXTENDED to an empty string, if it doesn't exist.

teo.tsirpanis.718's Avatar


20 May, 2019 08:58 PM

If the message of a commit is only one line long, the environment variable APPVEYOR_REPO_COMMIT_MESSAGE_EXTENDED does not exist. This meant that FAKE's AppVeyor library returned null, which crashes the build script if it is used improperly.

This was discovered to be the cause of a previously unresolved bug on a project of mine. As a workaround, the value is checked for null on my build script.

Given that environment variables represent important configuration data, that there is no other variable that may not exist, and that AppVeyor's documentation on environment variables mentions in the beginning "[e]nvironment variables that are set by AppVeyor for every build", my proposal is to always define the APPVEYOR_REPO_COMMIT_MESSAGE_EXTENDED variable, setting it to an empty string by default.

If it is not possible, I will take care to fix FAKE accordingly.

  1. Support Staff 1 Posted by Owen McDonnell on 21 May, 2019 05:32 PM

    Owen McDonnell's Avatar

    Thanks for bringing this to our attention.

    An issue has been created here

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac