Installing dependencies based on the appDependencyProbingPaths setting fail about al-go HOT 14 OPEN

This problem persists and several of our pipelines don't work so this is a big issue for us at the moment. Is there any indication on if and when you will be able to take a look at this?

from al-go.

Sorry about the delay
Looking at the log, I can see:

2024-05-03T05:17:44.6490538Z ##[warning]Some of the release tags cannot be recognized as a semantic version string (https://semver.org). Using default GitHub sorting for releases, which will not work for release branches

It ends up downloading release 4.12 of the bank pro app - is that the right one? (the latest)

These are the version it downloads and tries to publish to a container.

cust-pubsec-main-Apps-21.10.113.0.zip
datalager-connector-main-Apps-19.8.89.0.zip
bank-pro-main-Apps-4.12.1585.0.zip

and it looks like this dependency isn't resolved by any of those:

Consilia Solutions Ab_Public Sector Base_21.4.0.0.app

hence failing installation of Bank Pro.

Does this sound accurate?

from al-go.

Well, unfortunately no.

"Consilia Solutions Ab_Public Sector Base_21.4.0.0.app" is "cust-pubsec-main-Apps-21.10.113.0.zip" (not the same version but that should not be the problem).

I just ran a build in another repository that has the same issue and fewer dependencies. Attaching logs.

internal-deployer-job-logs.zip

from al-go.

Here is also the event log.
internal-deployer-main-ContainerEventLog-23.24.86.0.zip

from al-go.

Would it be possible to get the .zip file mentioned above to investigate why this fails?

from al-go.

I've sent a zip by e-mail.

from al-go.

Haven't received anything yet.
Maybe you need to send a URL from where I can download a file - not sure I can receive a .zip file with apps.

from al-go.

from al-go.

New info: If I use powershell instead of pwsh it works (by setting "shell": "powershell" in .AL-Go/settings.json).

from al-go.

Thanks for this info - will investigate

from al-go.

@kennetlindberg - could you share the log when running powershell?

from al-go.

Sure:
logs_24252696341.zip

from al-go.

There are a lot of other differences in the logs (than pwsh and powershell).
If you change the shell to pwsh - does it then fail again (on the same runners)

To me this looks more like a problem with the self-hosted runners than a problem with pwsh/powershell.

Could you maybe try using windows-latest / pwsh and see whether that fails?

from al-go.

Hi, here are a few comparable logs (there are no other changes except for the settings tested). They were run on our own server, but this problem started appearing back when we we running on a Azure virtual machine (created with a script I got from you) and also on freshly created runners.

powershell_logs_24377615426.zip
pwsh_logs_24376604210.zip
windows_latest_pwsh_logs_24378110537.zip

The only working one is "powershell".

from al-go.