Skip to content
This repository has been archived by the owner on Nov 14, 2023. It is now read-only.

Task not available for release definition? #71

Open
TASlavens opened this issue Aug 6, 2020 · 0 comments
Open

Task not available for release definition? #71

TASlavens opened this issue Aug 6, 2020 · 0 comments

Comments

@TASlavens
Copy link

Hello! From the Marketplace overview of the extension:

I find tagging or branching sources on every build is too much noise. There are so many builds that are just thrown away and never make it out of CI. I prefer to tag\branch when I get to a specific environment with the artifacts, usually UAT or production. This is a vsts plugin that will git tag or branch artifact source code with the release name.

I've installed version 9.0.0 of the extension into our non-production instance of on-prem AzDOS 2019u1.1p4 running on Win2016. The quoted text above strongly implies that the task should be available for release definitions, but here it is only available for build definitions. I have not tried it with a YAML pipeline, and in any case we have not moved to YAML yet, so that is not an option for us. From the questions on the Marketplace Q&A and a couple of issues here, it looks like this was not a problem in version 8.0.1 and earlier. Unfortunately, I haven't had time to dig into the task implementation.

Suggestions? Thanks in advance.

Regards,
Tom

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant