MicrosoftDocs / vsts-rest-api-specs

MIT License
166 stars 115 forks source link

undocumented endpoint '/_apis/distributedtask/pools/{pool id}/jobrequests' #568

Open Spoonsk opened 1 year ago

Spoonsk commented 1 year ago

The endpoint '/_apis/distributedtask/pools/{pool id}/jobrequests' is not documented. In our case we found it through github articles such as this.

We can use this endpoint to get all of the jobs performed for a given pool, however I'd like to know what other query string parameters this endpoint supports.

I verified this endpoint works and returns results as far back as API-version 6 (I didn't test lower than that)

Please update the documentation to detail this endpoint as well as what query parameters it supports


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

nechvatalp commented 1 year ago

Hello, this endpoint was meant to be for internal use only, that is why it is not publicly documented. We don't plan to make it public so there won't be documentation for this endpoint.

Spoonsk commented 1 year ago

Hello, this endpoint was meant to be for internal use only, that is why it is not publicly documented. We don't plan to make it public so there won't be documentation for this endpoint.

I see, thanks for the reply. Do you know where would be the best place to voice my opinion that this endpoint should be public? We have a business need to see recent jobs so we can:

Seems like others have similar needs given this endpoint making its rounds on SO and other tech forums.

nechvatalp commented 1 year ago

There is the Developer Community portal for submitting feedback and feature requests.

I will ping the team which owns this endpoint with your feedback so they are aware.

n-athan commented 7 months ago

Are there any plans to create a public endpoint to monitor this?

victorc-cylus commented 6 months ago

Many people use KEDA to run Azure Devops agents on Kubernetes, and KEDA depends on this endpoint: https://keda.sh/docs/2.13/scalers/azure-pipelines/

Please reconsider making it public, for documentation, and also to ensure it stays stable so integrations like these don't break if there are backwards-incompatible changes