-
Notifications
You must be signed in to change notification settings - Fork 206
FAQ
Typical questions about the Slack orb
Q: How can I stop duplicate messages in parallel jobs?
A:
It is not possible to limit the output to a singular output. The notify command acts as a convenient and parametrizable way to send a curl request to the provided Slack WebHook. When a job is ran in parallel, each instance runs independently and sends its own notification.
Q: Is it possible to receive only the final status of the Workflow?
A: Each job within a workflow operates independently, as the orb code executes within each job, they are not able to report on the outcome of the workflow after all jobs have completed. Each job can independently report its individual status.
Q: How do I use custom environment variables?
A:
Each step executes as a separate shell. To export environment variables for use in over steps, they must be added to BASH_ENV. View Using Environment Variables and the included usage examples.
Q: Can other orbs use this Slack Orb?
A:
If you would like to integrate with this orb from your own orb or service, we recommend hacking your orb generate a template.json file containing the payload of your desired message and saving the destination to an environment variable. Make sure to export the environment variable to $BASH_ENV. The user can then select the environment variable created as the template for the Slack Orb notification.
Q: Can I send to multiple channels?
A:
Yes, the channel parameter accepts a comma-separated list of channel IDs. By default, the Orb will attempt to post to $SLACK_DEFAULT_CHANNEL.
Q: Does it work on Alpine Linux?
A: Yes, but both CURL and JQ must be installed on the Docker image prior to running the Slack Orb.
Q: Does it work on Windows?
A:
Yes, support for Windows was implemented in v4.12.0. However, for it to work, you must use bash.exe as your executor's shell.