This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 70%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
We used a TFS 2015 server for many years, and only recently (last 12 months or so) upgraded to AZDO 2019 In the process, we appear to have lost the ability to upload new Build Task definitions, something that we do fairly infrequently, but when we need it, we need it. We use a script almost completely lifted from here: https://blogs.infosupport.com/custom-build-tasks-in-tfs-2015/ However, when we try it now, we get a 404 error.
GETting from _apis/distributedtask/tasks/{id} appears to work fine.
PUTting to it (to upload a new version of the task) is not working (returns 404)
I have modified the script to pass api-version=4.0 or 5.0, etc but can find no value that helps. I can find no mention anywhere of the /tasks API on any documentation pertaining to 2019 which is what I believe our server is running. All documentation for "modern" versions of AZDO seem to hint at /taskgroups as being something to investigate but none of those REST requests work either.
Where do I go from here? How do I determine the actual APIs that are being offered by our (onsite) AZDO Server?
Apologies for the perhaps-misplaced tag. Why is a tag MANDATORY in an environment where you don't have complete coverage of every possible topic in the world?
This site is tag based so without tags there would be no origination and no method to filter threads.
If the document is lacking info or in error I'd use the Site Feedback link and post the details over here. I've reported several and they're generally responsive to the reports.
https://github.com/MicrosoftDocs/feedback/issues
to the issue I'd ask in forums over on DeveloperCommunity
--please don't forget to Accept as answer if the reply is helpful--
So, to address a Microsoft documentation deficiency, I need to create a github account as well?
Sigh.
Ok, marking this as the answer, but underwhelmed at Microsoft in general
Yea, microsoft aquired github and of course we need to have a separate profile for almost every service.
Devops / TFS is not currently supported here on QnA. The product group for Azure DevOps / TFS actively monitors questions over at
https://developercommunity.visualstudio.com/spaces/21/index.html
https://developercommunity.visualstudio.com/spaces/22/index.html
--please don't forget to Accept as answer if the reply is helpful--
Is that really an appropriate answer about a deficiency in the documentation, being queried on the documentation site?
I came here because the documentation for TFS 2019 is both incomplete (no mention of /tasks/ which does exist in the software) and wrong (it mentions /taskgroups/ which does not exist in the software as far as I can tell).
In fact, the manner in which the documentation is provided on the many versions of TFS just highlights what a bad idea versioning web api's is (or perhaps just how poorly it has been executed). A purple banner at the top of the page saying (effectively) "The api-version you asked about doesn't do this, so I'm showing you something different" is ludicrously poor UI for a documentation site.
What I'm looking for is accurate documentation on AZDO 2019 which seems to be something this site claims to document.
Is that really an appropriate answer about a deficiency in the documentation
Well they closed the TFS uservoice site and moved feedback over to DeveloperCommunity links I posted.
https://developercommunity.visualstudio.com/spaces/21/index.html
https://developercommunity.visualstudio.com/spaces/22/index.html
--please don't forget to Accept as answer if the reply is helpful--
ISorry, I should have said "thanks for the link", from what I can see, the problem is that they have apparently changed the base address of the Web Service (though I have not confirmed that in code yet).
But whether that's right or not, the documentation site is wrong and I assume they (that other team) are not tasked with keeping it up to date.
the documentation site is wrong
What site and documentation are you asking about here?
This one.
For example, try to find a definition of the /distributedtask/tasks api for DEVOPS 5.0 (which is what I believe AZDO2019 is)