Queue Build for user that triggered original build Option superseded by Personal Access Token User

[brianroche]

After upgrading to Version Azure DevOps Server 2022.2 (AzureDevopsServer_20240806.7), Queue Build for user that triggered original build option that is checked does not occur. Triggered build now shows user credentials used in PAT under authentication as initiated user instead,

[huserben]

Hi @brianroche

Thanks for reporting this. As I do not use Azure DevOps Server, it's hard to tell what the issue is.
My best guess is that Microsoft might have adjusted the API and with the change it might either not be supported anymore or a change is needed in the API calls. Another option could be that some security settings might have changed with your upgrade and that is somehow interfering. But I'm just guessing...

I'm not actively using the task anymore, thus I also don't spend a lot of time on it. I will try to investigate, but can't promise that I will be able to provide any fix for this.

In general I'd recommend to use the built-in OAuth Token and trigger pipelines via the build service wherever possible, that seems to work best (as for example PATs do expire and need to be renewed, which is a source for pipeline errors). Is moving to the built-in OAuth authentication and using the Build Service an option for you?

[brianroche]

Hi @brianroche

Thanks for reporting this. As I do not use Azure DevOps Server, it's hard to tell what the issue is. My best guess is that Microsoft might have adjusted the API and with the change it might either not be supported anymore or a change is needed in the API calls. Another option could be that some security settings might have changed with your upgrade and that is somehow interfering. But I'm just guessing...

I'm not actively using the task anymore, thus I also don't spend a lot of time on it. I will try to investigate, but can't promise that I will be able to provide any fix for this.

In general I'd recommend to use the built-in OAuth Token and trigger pipelines via the build service wherever possible, that seems to work best (as for example PATs do expire and need to be renewed, which is a source for pipeline errors). Is moving to the built-in OAuth authentication and using the Build Service an option for you?

Thanks for the quick reply! I just attempted to use the OAuth Token and build service, but unfortunately that now shows as the Project Collection Build Service for the build that was triggered and not the originating user. I don't have the ability to test via basic auth but I would presume that the update affected the option for all authentication types.

[huserben]

Thanks for checking - it was worth a try I guess...

I think basic auth might even be not supported anymore (if my memory serves me right, Microsoft was trying to out phase this...).
Which version of the task are you using? And were you using the same task before or is it a different version (if you happen to know)?

[brianroche]

We were using version 3 of the task prior to and after the upgrade. After getting reports of the issue we tried changing one instance to version 4 of the task and still had the issue.

[huserben]

Ok, not sure what could be wrong then. Could you share the logs? Is it properly identifying the user in the logs?

[sdound]

@huserben @brianroche We recently upgraded our Azure DevOps Server to version 2022.2.2, and we started experiencing issues with all our existing builds that use the TriggerBuild task. I’ve tried all three authentication modes, but in every case, it uses the authentication user instead of the user who triggered the parent build. Could you please confirm when a fix for this issue will be available?

[huserben]

Hi @sdound

Sorry to hear about your struggles. I'm not actively maintaining the tasks anymore, as I'm not working with Azure DevOps at the moment and can not really test.

Thus, my advice would be to check out other tasks that achieve the same, as I won't be able to provide any extended support or look into the code and make a change in the near future.