Closed aspiringtfsguru closed 3 years ago
Here is an example snippet of a build definition that gets return and one that does not.
This build definition has an agent pool that is not null and it gets returned:
"queue": {
"_links": {
"self": {
"href": "https://dev.azure.com/**************/_apis/build/Queues/377"
}
},
"id": 377,
"name": "On-Prem",
"url": "https://dev.azure.com/**************/_apis/build/Queues/377",
"pool": {
"id": 10,
"name": "On-Prem"
}
}
This build definition has an agent pool that IS null and it does not get returned:
"queue": {
"_links": {
"self": {
"href": "https://dev.azure.com/**************/_apis/build/Queues/203"
}
},
"id": 203,
"url": "https://dev.azure.com/**************/_apis/build/Queues/203",
"pool": null
}
EDIT: Had a typo that needed fixing.
Now that I think about it, I should probably just catch that on my side.
The question actually is when this comes actually up?
Is it only when you create a pipeline with the json, the API or over the GUI.
In the case of the latter, I could imagine the this should return it.
Steps to reproduce
If a build definition does not have an agent pool assigned (it can happen), those definitions will not get returned.
Expected behavior
Actual behavior
Environment data
OS
Server