search

huserben / TfsExtensions

Extensions for TFS 2015+ such as custom Widgets (require TFS 2017) and Build Tasks
MIT License
44 stars 22 forks source link

Trigger Build - queueid does not seem to have an effect #222

Closed swerve92 closed 1 year ago

swerve92 commented 1 year ago

Hi

Trigger Build used to work fine for us, but we didn't use it for a while and now when I try to use it I have noticed the triggered builds are running on the wrong agent pool (the default one).

When Trigger Build is run, its log contains the following:

Will trigger build in following agent queue: 244 (244 is the correct id for the agent pool that I want the build to run on)

But when I follow the link for the queued build and I check the agent pool, it is just being queued on the default pool for the build defintion.

huserben commented 1 year ago

Hi @swerve92

Sorry for the late reply, I'm currently on vacation. Thus I can also not dig deeper on the described issue.

What you could try is using the pool name instead of the ID. Perhaps there is a rights issue that is making it behave strangely.

From the docs: Note: When specifying a Queue you have to make sure that the user triggering the build has no access to it, for example when using the OAuth Authentication Method. This is the case when the error Error message: Error: No agent pool found with identifier 769 is shown. An option to work around this would be to switch to Personal Access Token Authentication and making sure that the Token has enough access rights

Maybe the behaviour from ADO has changed and now it's defaulting to the default pool...

huserben commented 1 year ago

Hi @swerve92

any update on this?