Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-13816

Detailed Slack and Stride notifications for deployments in Pipelines

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      We're using the Slack notifications for completed pipelines integration outlined here: https://bitbucket.org/snippets/xtjhin/GpkxB

      We recently moved over to using pipelines from DeployBot and we really miss the commit messages from the notifications because it's useful to keep track of what exactly is going out in each deploy.

      In addition to the branch and the status of the build we would love the following information:

      • Commit Message - Ideally parsed as Markdown and JIRA ticket references hooked up.
      • Commit Hash
      • Build Status
      • Whether the deployment was automatic or manually triggered
      • Who the commit author was that triggered the build

      In addition there is a lot of extraneous information in the messages which make it harder to keep track of what is actually going on when you're doing lots of deployments. E.g. "Build status updated to SUCCESSFUL" could be shortened to just "Status: SUCCESSFUL".

      The "In Progress" notifications are a bit of a distraction too when looking back through the logs so it would be good to be able to separate those from the build success/fail ones.

      See attached images for an example.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            b8f48d3a1300 ssibelle
            Votes:
            17 Vote for this issue
            Watchers:
            27 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: