The update command is the default command. It is used inside your CI jobs in order to execute the updates triggered by Pmbot.



CLI Option: --token <token>, -t <token>

Environment variable: PMBOT_TOKEN

Default: none, required

Token used to authenticate with the API.


CLI Option: --ssh-private-key <path>, -k <path>

Environment variable: PMBOT_SSH_PRIVATE_KEY

Default: none, required

Path to the SSH private key for pushing to the git current repository.

You can generate a new SSH key pair with the following command:

ssh-keygen -b 4096 -t rsa -f /tmp/sshkey -q -N ""

Make sure you add the corresponding public key to your git project.


CLI Option: --url <url>, -u <url>

Environment variable: PMBOT_URL

Default: https://app.pmbot.io

The URL to the instance of Pmbot used for the update (e.g. https://pmbot.company.com or https://company.com/pmbot)


CLI Option: --disable-host-key-verification [true|false]


Default: false

Disable host key verification when using git over SSH.


CLI Option: --plugins <name> [--plugins <name>] ..., -p <name> [-p <name>] ...

Environment variable: PMBOT_PLUGINS

Default: none

Only one plugin can be added the environment variable due to a limitation in yargs. If you need to use multiple plugins, please use CLI arguments.


CLI Option: --config <path>, -c <path>

Environment variable: PMBOT_CONFIG

Default: .pmbot.yml

Path to the Pmbot config file.


CLI Option: --workdir <workdir>, -w <workdir>

Environment variable: PMBOT_WORKDIR

Default: .

The directory where Pmbot will find the cloned repository of the project to update.

#Self signed certificates

If you are using self-signed certificates to secure your servers (i.e. Pmbot, package repositories...), you'll want to set the NODE_EXTRA_CA_CERTS environment variable with the path to a trusted Certification Authority certificate.

This CA should have the pem format: