CircleCI Ideas

Revamped Slack notifications for Workflows (2.0)

Slack integration is really neat, yet with the introduction of workflows in 2.0, it creates a lot of spam because each job will create its own notification

It would be nice if either of the changes would be made:

  • Trigger a single notification containing 

- Name, status and link to each individual job of a given workflow
- Name of the workflow as well as a link to its workflow-run

  • If notifications must be per individual job, then notification content should include:

- Name of the job 
- Name of the workflow as well as a link to its workflow-run

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Feb 2 2018
  • Shipped
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    7 Aug, 2019 06:43pm

    +1, and would like more ability to customize slack notifications, specifically, including env vars that were passed in, and what branches to notify.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 Jan, 2019 06:53pm

    +1 I'd really love to send notifications for certain branches and not others, e.g. master only.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Nov, 2018 08:37pm

    Will live updates as described in https://circleci.ideas.aha.io/ideas/CCI-I-231 be available soon? I'm only seeing notifications when a workflow is finished.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Nov, 2018 07:37pm

    thanks, Kunal! 

    Is there a way to only get notifications for a particular branch (e.g. master) or status (e.g. fixed or failed) ?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Nov, 2018 07:18pm

    We have rolled out workflow level slack notifications for all customers. As mentioned in the original idea we have added a name, status and link of workflow with a link to a failed job within that workflow.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Oct, 2018 11:33am

    Would be great if we can send a notification with embed button to unhold directly in slack step of type approval.

    Also, being able to deliver notification to a specific slack channel depending on branch, etc..

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    5 Oct, 2018 12:04am

    Please enable for raptor235 thank you

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    4 Oct, 2018 10:25pm

    Hello!

    We are starting an early beta for slack notifications. If you are interested, please email your GitHub or Bitbucket organization name at beta@circleci.com and we can enable slack notifications from your organization.

    Thank you so much for your patience.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    12 Sep, 2018 09:48pm

    @Kunal Jain

    What is the status on this ? What does early Q4  mean ?


    You forced  all of us to move to 2.0 by August 31st and now essentially Slack notifications are unusable. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 Aug, 2018 06:04pm

    We are working on revamping slack and email notifications for workflows. This feature should be available by early Q4. Thank you so much for your patience. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 Aug, 2018 07:24am

    I've submitted a support request. That ticket requests an update on the time horizon for this feature. Will get back to you with their responses.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    15 Aug, 2018 09:25am

    Any update on when this feature might make it to release? 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    9 Aug, 2018 04:04pm

    If it's also about never replying, you could have kept this "ideas" section in the Discuss forum.

    The current Slack integration is a shame, it can't be that hard to send one message instead of N.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 Aug, 2018 09:08am

    I like the fact that it says this is planned, but could there be an indication of a likely implementation date? It would allow us to evaluate the worth of implementing our own workaround

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    31 Jul, 2018 12:48pm

    Has there been any official response regarding this issue? I'm noticing it now during switching a pipeline over. Notifications are really noisy in their current state for workflows that involve more than a few jobs.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Jul, 2018 04:01pm

    Does this also involves targeting specific branches? e.g. master only Slack notifications.

    If not, can anyone please point me to a doc for that?

    I'd love for my team to become more aware of master failures without getting spammed of not-so-important branches that have failed. thanks!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Jul, 2018 08:48am

    So here is my issue with the existing implementation

    • The information is of little or no value
    • It's spams the channel on a real life workflow
    • The status returns false positives, zero value in that as well

     

    There is no denying the usefulness of workflows but we have also come to rely on the slack notifications as well, particularly off hours. As it stands right now, imo they tarnish what is an otherwise extremely powerful feature.

     

    There is an example of my smallest build in the attached screenshot, it's hard to find value in that information. Particularly when two of those steps actually failed.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Jun, 2018 02:03am

    That's crazy spam, I am disabling Slack integration. Could you please fix that?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    9 Jun, 2018 05:18am

    I hate people who just write "+1" without adding any value to the thread.

     

    But I will be one anyway. Is anyone looking at this bug? Is there any prognosis for fixing it? Sorry, I don't time time or bandwidth to replace these broken slack and email notifications with ones of my own. Why was this not a basic feature implemented as part of 2.0? Is anyone there? HELLO??

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    6 Jun, 2018 05:19pm

    Missing this feature. Also, the capability to set filter branch to not receive all branchs (nightly builds, development) notifications.

  • Load older comments