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
CI Pipeline building app with dependency on 3rd party symbol extension errors with "Unable to locate the server instance: MicrosoftDynamicsNavServer$BC"
#3764
Describe the issue
I have a CI pipeline in DevOps that was produced using the hands on labs. I'm trying to get it working on an extension that has a dependency on a 3rd party extension. It was developed via installing the 3rd party AppSource extension into the cloud environment. Adding the dependency in the launch.json and downloading the Symbol file.
I've provided the symbols.app file to the install apps parameter in my pipeline and got the same issue reported here #3717
I then added the -doNotPublishApps parameter to Run-AlPipelinecommand in the DevOps-Pipeline.ps1 file and the pipeline now successfully compiles the app and produces the artifact. However, it now errors while getting the runtime package for the newly compiled app
2024-11-15T06:33:12.4771721Z Getting Runtime Package for BC Dev Test_Hello World_1.0.0.36609.app
2024-11-15T06:33:13.6726647Z Unable to locate the server instance: MicrosoftDynamicsNavServer$BC
I reproduced the issue in a spike HelloWorld app to make sure it wasn't anything particular to the extension itself.
Scripts used to create container and cause the issue
Scripts used are from the DevOps Hands On Labs, hooked up to a CI pipeline in DevOps.
does it happen all the time? Yes - For those apps that have 3rd party dependencies and where we only have access to the downloaded symbol file. Which is enough for the IDE compiler.
did it use to work? No - I haven't yet been able to successfully get an app with a 3rd party dependency and provided symbol files working. But then, I've probably been barking up the wrong tree 😀
The text was updated successfully, but these errors were encountered:
Describe the issue
I have a CI pipeline in DevOps that was produced using the hands on labs. I'm trying to get it working on an extension that has a dependency on a 3rd party extension. It was developed via installing the 3rd party AppSource extension into the cloud environment. Adding the dependency in the launch.json and downloading the Symbol file.
I've provided the symbols.app file to the install apps parameter in my pipeline and got the same issue reported here #3717
I then added the -doNotPublishApps parameter to Run-AlPipelinecommand in the DevOps-Pipeline.ps1 file and the pipeline now successfully compiles the app and produces the artifact. However, it now errors while getting the runtime package for the newly compiled app
I reproduced the issue in a spike HelloWorld app to make sure it wasn't anything particular to the extension itself.
Scripts used to create container and cause the issue
Scripts used are from the DevOps Hands On Labs, hooked up to a CI pipeline in DevOps.
Settings.json
Excerpt from DevOps-Pipeline.ps1 script showing additional -DoNotPublishApps parameter
Full output of scripts
See attached file PipelineRawOutput.txt
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: