Closed walkerjono closed 1 year ago
Could you use Get-BcContainerEventLog to see if the event log reveals any reason why BC cannot import the license? (I do think importing the license is the problem and maybe the servicetier crashes as a result of this - testing myself now)
Tested the version you have above and my license works fine. Need the eventlog to continue, thanks
Thanks very much for the quick reply.
I've actually never retrieved the event log from the docker container in an Azure DevOps pipeline. I've successfully added the additional task to call the Get-BcContainerEventLog
, but realised that the event log is in .evtx
format (after reading the docs)
If you can point me in the right direction to retrieve the contents of the event log from the pipeline that would be very much appreciated. If not, I understand and will continue to figure it out and revert back.
Thanks again
Can't you publish the .evtx file as an artifact and download it from Azure DevOps? You might also be able to add -dumpEventLog to your New-BcContainer and then use docker logs containername to get the logs - which should include the eventlog then.
This is a bug in the Service Tier, due to this setting:
-e CustomNavSettings=ServicesUseNTLMAuthentication=true
What is the reason for that setting?
Thanks very much.
That setting is set by:
-additionalParameters @("-v $($RepoPath):c:\app",'-e CustomNavSettings=ServicesUseNTLMAuthentication=true')
Why, I'm unsure. I'll raise it with the developer of the library.
I'll also switch the container creation to use the New-NavContainer
without the NVRAppDevOps abstraction and report back.
Thanks again for your assistance
Thanks for the info, I was just looking into this yesterday and today and I am lucky I found this Issue. Code in NVRAppDevOps was adjusted and this parameter is no longer used by default in v2.4.0.
Amazing, thanks for the updated library @kine .
I've successfully re-run my pipeline with the update libarary and the previously failing artifact now passes:
Get-BCArtifactUrl -country nz -version 22
, which returned22.5.59966.61111
, and thanks very much for the assistance guys, its much appreciated!
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue I have an Azure DevOps pipeline that has been running happily. It uses a mixture of https://github.com/kine/NVRAppDevOps and
navcontainerhelper
Powershell commands, and runs on a hosted agent only.One of the team notified me that builds started failing on 2023-10-02, we quickly identified that the BC license had expired the previous day. The license was renewed and updated in the pipeline, however builds continued to fail when creating the docker container.
Through much trial and error, I think something has changed in the underlying BC artifact that is causing the build to fail when creating the docker container.
I say this as I can replicate and workaround the issue by running the exact same build, but pinning the build to a specific BC Artifact version that was working as of Friday 29 September, and it will create the docker container and compile the extension successfully. If I take the latest v22.x BC artifact it will fail when creating the docker container, with nothing else changed.
Pinned Version (docker container created and compiles successfully)
Get-BCArtifactUrl -country nz -version 22.5.59966.60900
... 10 other versions ...
Latest v22.x Version (docker container creation fails)
Get-BCArtifactUrl -country nz -version 22
Based on the above, the only things that have changed are:
-version 22.5.59966.60900
-version 22
If you need further information or would like me to re-attempt any builds, please let me know and I'd be happy to provide the info. Thank you! Scripts used to create container and cause the issue I understand that the following is an abstraction over
New-NavContainer
using NVRAppDevOps . If required, I can convert this to the actualNew-NavContainer
command, however, I don't see how this would make a difference, but I'd be happy to attempt it if you think it would be helpful?Full output of scripts
Pinned Version (docker container created and compiles successfully)
Get-BCArtifactUrl -country nz -version 22.5.59966.60900
Latest v22.x Version (docker container creation fails)
Get-BCArtifactUrl -country nz -version 22
Additional context