Make Task Groups available via the REST API
Just like we can get things like a list of release definitions via the REST API ("/_apis/release/definitions") I would like the Task Groups to be made available in the same way:
Get a list of task groups
Get a task group
Create a task group
Update a task group
Delete a task group
Get revision history for a task group
Get a particular revision history
We are happy to let you know that your suggestion is now available on Team Services. It will become available to the on-prem version in TFS 2018 Update 2.
Anonymous ( December 27, 2017 07:30), thanks for the link to the samples: https://github.com/Microsoft/vsts-dotnet-samples/pull/90/files
Be aware that this code sample is a little different from the latest version (15.134.0-preview). Instead of a TaskGroup you must create a TaskGroupCreateParameter. The Task property does not need to be created in that instance. You can add the taskGroupStep at once.
Bryan Johnson commented
This is currently NOT in TFS 2017 or any of its updates? If we want this functionality we'd need to use TFS 2018?
Frank van Eykelen commented
That's great news. Thanks!
John Beard commented
Would also be nice to export/import task groups via API
Few of the API's are in the process of getting documented. But irrespective of documentation, the client is already getting released via nuget https://www.nuget.org/packages/Microsoft.TeamFoundation.DistributedTask.WebApi/. You may take a look into the samples at https://github.com/Microsoft/vsts-dotnet-samples/pull/90/files as how to use it.
I dont understand why such basic functionalities required a voting, and our existing CI/CD runs on Jenkins and never created any pipeline using UI. We are currently evaluating VSTS for our new Infra and definitely, such API limitations will be a downvote.
Would be nice if we could update variable groups via the REST API
I couldn't find the documentation myself but looking at Developer tools or Fiddler you can look at the usages _apis/distributedtask/taskgroups
I don't understand how this feature even got released without any api to access it...