Hi, this seems to work great for "Pipelines", adding a custom task to all builds for example. However it does not work on releases. Is there a way to get it to work? The target for pipelines is ms.azure-pipelines-agent-job.pre-job-tasks. Is there an equivalent for releases? I want to enforce a task whether a user is running a build, multi-stage yaml build/release, or just a release.
Thanks,
Matthew
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hey Matthew,
This does not exist for releases yet. We have plans to add it in the future but I don't know what the timeline is. It should work today for build and multi-stage build/release.
Stephen
Thanks for the update!
Hi @stephenmichaelf , are you aware of any updates to this planned feature?
I'm on the build team at a large corporation, and one of the things we'd like to do is gather statistics on how many releases are done daily and what kinds of technologies are in use. For example, what % of our applications are .NET and hosted in Azure. This release decorator would be perfect for that, since we could drop it into everyone's releases without them needing to do anything.
@lettucemode They've been added! Let me find out if we've updated the docs for how to use them.
I've reached out to the team that implemented decorators for release and asked them to respond here with steps and to updated our docs here.
@lettucemode we have added the info in this document. You can find info on what to add as targets, _ms.azure-release-pipelines-agent-job.pre-job-tasks_ and _ms.azure-release-pipelines-agent-job.post-job-tasks_ targets inject the decorators in jobs in release pipelines. This feature is enabled for everyone, once you opt-in the decorator-preview.
We also have few more details on this in this decorator expression context also.
Thank you both!