Wow! This worked! (even though we don't use our own VMs, but Azure DevOps by Microsoft)
>>> AZURE_CLIENT_ID AZURE_CLIENT_SECRET and AZURE_TENANT_ID
I guess you can't name your Azure DevOps variables anything other than this, so renaming them exactly like this worked! Hallelujah, and THANK YOU!
Suggested Articles
Search found 4 matches
- Wed Jul 31, 2024 3:10 pm
- Forum: Building Installers
- Topic: Enable Trusted Signing causes YAML pipeline to hang for an hour
- Replies: 7
- Views: 30322
- Jump to post
- Mon Jul 29, 2024 3:45 pm
- Forum: Building Installers
- Topic: Enable Trusted Signing causes YAML pipeline to hang for an hour
- Replies: 7
- Views: 30322
- Jump to post
Re: Enable Trusted Signing causes YAML pipeline to hang for an hour
That link doesn't have anything to do with Automation such as YAML pipelines in Azure DevOps.
(It does have some useful info for manually building on a PC and using local ENV Variables, though: AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and AZURE_TENANT_ID)
Are you implying you think the pipeline build ...
(It does have some useful info for manually building on a PC and using local ENV Variables, though: AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, and AZURE_TENANT_ID)
Are you implying you think the pipeline build ...
- Fri Jul 26, 2024 7:22 pm
- Forum: Building Installers
- Topic: Enable Trusted Signing causes YAML pipeline to hang for an hour
- Replies: 7
- Views: 30322
- Jump to post
Enable Trusted Signing causes YAML pipeline to hang for an hour
I need help to figure out why simply clicking Enable signing and choosing Use Trusted Signing (and filling out the correct info for End Point, Account Name, Certificate Name, of course) makes the YAML step hang for an hour, which gets killed by Azure DevOps.
It normally take 8 minutes to run the ...
It normally take 8 minutes to run the ...
- Tue Dec 01, 2020 5:47 pm
- Forum: Common Problems
- Topic: VS2019 throws the 'AdvInstVSIntegrationPackage' package did not load correctly error.
- Replies: 5
- Views: 5543
- Jump to post
Re: VS2019 throws the 'AdvInstVSIntegrationPackage' package did not load correctly error.
Upgrading Visual Studio 2019 to the very latest worked for me, too.