Answers: <p>The stock <em>Azure Pipelines app for Slack</em> does not support that workflow of uploading artifacts to Slack. You could use <a href="https://marketplace.visualstudio.com/items?itemName=kasunkodagoda.slack-notification" rel="nofollow noreferrer">this marketplace</a> task and upload your release notes artifact with it.</p>
  
  <p>Bonus points suggestion, if you are going down the release notes path I would take a look at using Richard Fennell's <a href="https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-XplatGenerateReleaseNotes" rel="nofollow noreferrer">Generate Release Notes task</a> in combination with the <a href="https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-WIKIUpdater-Tasks" rel="nofollow noreferrer">Wiki Updater task</a>.  </p>
  
  <p>You can create a generalized Task Group or yaml template that you could pretty much re-use anywhere. For example in the Wiki updater task you can create a release name wiki page formatted like:
  <code>$(Build.Repository.Name)\$(Release.EnvironmentName)\$(Release.ReleaseName).md</code></p>
  
  <p>And then in your Slack message send a generalized link to your release notes.
  <code>Release Notes Wiki link &lt;https://collection-name.visualstudio.com/projectname/_wiki/wikis/Release-Notes?wikiVersion=GBmaster&amp;pagePath=$(Build.Repository.Name)\$(Release.EnvironmentName)\$(Release.ReleaseName)|$(Release.EnvironmentName)\$(Release.ReleaseName)&gt;</code></p>
  
  <p>You could push them back into the Repo that the release originated from or a central release notes repository. Your release notes get source controlled and are nicely organized!</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-01-24T06:31:13.840Z
Answers: 2020-01-24T06:31:13.840Z
Answers: Eric Smith
Body: <p>I have a pipeline on Azure DevOps that publishes an artifact (<code>releasenotes.txt</code>). </p>
  
  <p>It also has integration with Slack using ( <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/integrations/slack?view=azure-devops" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/devops/pipelines/integrations/slack?view=azure-devops</a> ) . </p>
  
  <p>How can I send <code>releasenotes.txt</code> to Slack? Is it possible?</p>
  
Tags: <azure-devops><build-pipeline><azure-pipelines><artifacts><slack>
Title: Publish pipeline artifact to Slack
UserDisplayName: user1202032
ThreadText: # Publish pipeline artifact to Slack
  
  (Asked by: username_0 on 2020-01-11)
  
  I have a pipeline on Azure DevOps that publishes an artifact (`releasenotes.txt`).
  
  It also has integration with Slack using ( <https://docs.microsoft.com/en-us/azure/devops/pipelines/integrations/slack?view=azure-devops> ) .
  
  How can I send `releasenotes.txt` to Slack? Is it possible?
  
  **Tags:** azure-devops, build-pipeline, azure-pipelines, artifacts, slack
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-01-24. Score: 2 | Accepted answer
  
  The stock *Azure Pipelines app for Slack* does not support that workflow of uploading artifacts to Slack. You could use [this marketplace](https://marketplace.visualstudio.com/items?itemName=kasunkodagoda.slack-notification) task and upload your release notes artifact with it.
  
  Bonus points suggestion, if you are going down the release notes path I would take a look at using Richard Fennell's [Generate Release Notes task](https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-XplatGenerateReleaseNotes) in combination with the [Wiki Updater task](https://marketplace.visualstudio.com/items?itemName=richardfennellBM.BM-VSTS-WIKIUpdater-Tasks).
  
  You can create a generalized Task Group or yaml template that you could pretty much re-use anywhere. For example in the Wiki updater task you can create a release name wiki page formatted like:
  `$(Build.Repository.Name)\$(Release.EnvironmentName)\$(Release.ReleaseName).md`
  
  And then in your Slack message send a generalized link to your release notes.
  `Release Notes Wiki link <https://collection-name.visualstudio.com/projectname/_wiki/wikis/Release-Notes?wikiVersion=GBmaster&pagePath=$(Build.Repository.Name)\$(Release.EnvironmentName)\$(Release.ReleaseName)|$(Release.EnvironmentName)\$(Release.ReleaseName)>`
  
  You could push them back into the Repo that the release originated from or a central release notes repository. Your release notes get source controlled and are nicely organized!
  
  
  ---
  
  