Outgoing web-hooks

This release added support for outgoing web-hooks. Outgoing web-hooks can be used to automate your external workflows. For example, you can send messages to a Slack Channel or trigger Selenium test automation upon completions of a CI job within ClickDeploy.

To enable web-hooks, go to Deploy Options > more > enable outgoing web-hooks.

Screen_Shot_2019-08-28_at_11.49.32_AM.png

After enabling outgoing web-hooks, go to the "Outgoing Webhooks" tab and fill in the detail as below. In the "Payload" section, you can reference to variables such as
$DEPLOYMENT_ID, $DEPLOYMENT_TITLE, $DEPLOYMENT_STATUS and ClickDeploy will replace these by the actual deployment Id and deployment title before posting the message to your external service.

When enabled, outgoing web-hooks will be triggered for each validation or deployment action. It will be triggered irrespective of whether the action is scheduled or manual.

Screen_Shot_2019-08-28_at_11.48.40_AM.png

Git commit author's email

For SSH repo, you can now specify a Git User Email in addition to the Git Login (or Git Username). These will be reflected in your commit message as part of the author and committer details.

Screen_Shot_2019-08-28_at_11.51.51_AM.png
Did this answer your question?