SteveKrisjanovsD365
commented
5 days ago Disregard this. it seems there were org-level AL Go settings that were interfering with the build pipeline. I'm going to repro without any AL-Go org settings overrides. If an issue arrises I'll submit a new github issue
AL-Go version
6.0
Describe the issue
we're having a problem with the CICD >> build pipeline for PTE repositories that depend on third party PTE apps.
We have an AL Go PTE project-based repo. it depends on third party PTE apps, which we declared in .project1.AL-Go\settings.json >> "installApps" property (each app in the array is a URL to a VSCode-compiled app. not a runtime pkg).
the "install apps" step succeeds (it downloads and installs each app to the BC container), but the subsequent "build step" fails
we also tried moving the "installApps" property to .github\AL-Go-Settings.json. same result: install apps succeeds, build step fails
the third party PTE dependency in this case is a full app file compiled from VS Code (not a runtime pkg nor app symbol). we are using github-hosted runners (not local runners)
the follolwing workshop markdown to explain how to handle externally-hosted third party dependency PTEs (not as git repos but as downloadable app URLs) is also inomplete: https://github.com/microsoft/AL-Go/blob/main/Workshop/Dependencies3.md
Expected behavior
build pipeline should succeed
Steps to reproduce
request fork access to https://github.com/365Vertical/HelloWorldMultiAppPTE to fork+repro
otherwise do this:
Additional context (logs, screenshots, etc.)
see the following CICD log which I attached to this ticket: job-logs.txt
note how the "install apps" step succeeds (it downloads and installs each app URL defined in "installApps"), but the build step fields. See the following log entries to jump to the errors raised: