You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a single cloud VM build agent attached to ADO that allows for parallel pipeline runs. Microsoft PowerPlatform CLI
Version: 1.39.3+g0f45f92 is installed.
When a single pipeline is running, authenticating to a power platform environment works 100% of the time, whether by using ADO yml power platform tools, or using pac.exe directly through yml ps1 scripts.
When multiple pipelines are run at the same time, 50% of the time pac auth will confuse authentication. The proper environment will be selected, but when trying to perform an action on the env, it will be pointing to what the other pipeline authenticated as (notice the two Connected to lines in the log below). This auth error happen even if one yml is using ADO build tools and another is accessing pac.exe directly (which makes sense, it's the same exe/libs underneath):
Create env id:
env_impleo-dev-main-gac
Authenticating
Authentication profiles and token cache removed
'bfafd489-5698-4457-98b7-cde9ad4557a0' authenticated successfully.
Validating connection...
**Connected to... IMPLEO_DEV_MAIN_GAC**
Default organization: IMPLEO_DEV_MAIN_GAC
Authentication profile created
* UNIVERSAL env_impleo-dev-main-gac : bfafd489-5698-4457-98b7-cde9ad4557a0 Public https://impleo-dev-main-gac.crm3.dynamics.com/
New default profile:
* UNIVERSAL env_impleo-dev-main-gac : bfafd489-5698-4457-98b7-cde9ad4557a0 Public https://impleo-dev-main-gac.crm3.dynamics.com/
Connected as 2bb44b1a-b9c5-4d71-ab32-ef6041385fd7
**Connected to... DXP_TCS_QA2_GAC**
No Power Pages website records exist
I did not provision our BuildAgent, so I don't have all the details on hand, but I can find out. I can't imagine it possible that, when setup correctly, pac.exe does not support concurrent authentications across ADO pipeline runs. This error has happened across multiple versions of pac build tools.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have a single cloud VM build agent attached to ADO that allows for parallel pipeline runs. Microsoft PowerPlatform CLI
Version: 1.39.3+g0f45f92 is installed.
When a single pipeline is running, authenticating to a power platform environment works 100% of the time, whether by using ADO yml power platform tools, or using pac.exe directly through yml ps1 scripts.
When multiple pipelines are run at the same time, 50% of the time pac auth will confuse authentication. The proper environment will be selected, but when trying to perform an action on the env, it will be pointing to what the other pipeline authenticated as (notice the two Connected to lines in the log below). This auth error happen even if one yml is using ADO build tools and another is accessing pac.exe directly (which makes sense, it's the same exe/libs underneath):
I did not provision our BuildAgent, so I don't have all the details on hand, but I can find out. I can't imagine it possible that, when setup correctly, pac.exe does not support concurrent authentications across ADO pipeline runs. This error has happened across multiple versions of pac build tools.
Any help would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions