Troubleshooting

Deployment did not start
If you received a Slack notification telling that deployment did not start, make sure that:
The .slashdeploy.yml file is configured properly.
The repository you're trying to deploy has been installed via our GitHub App.
The repository has configured to handle deployment events.
The service handling deployment events is working and sending Deployment status updates correctly back to GitHub.
Environment is not recognized
If neither /deploy where nor /deploy commands recognize the environment you have defined in the .slashdeploy.yml file, make sure that the configuration file has been pushed to the GitHub's default branch. SlashDeploy syncs up configuration changes only from the default branch.
Deployment hung
If you received a Slack notification telling that deployment hung, make sure that all the required status checks listed in the .slashdeploy.yml file are not stuck in pending state in GitHub. Try to transition these checks to either success, failure, or error and your deployment will likely continue.
Slack notifications do not appear in the channel
If you've configured default_channel or environment-specific channel to receive deployment notifications, but they are still sent as direct messages, make sure that you've invited @slashdeploy bot user to the respective channel. You can use Slack's internal command to do so:
/invite @slashdeploy [channel]

Last modified 4yr ago