[Bug]: Deploy job skips in multi-project solution

[BeytullahCengiz88]

AL-Go version

Preview

Describe the issue

When the CI/CD pipeline runs the Deploy step is not triggered in multi-project solutions.
I have a W1 app on top of 2 apps: GB and PL

Here are my trial/error steps to get work this:
In the W1 app

• in the W1 AL-Go settings: I have declared environments in array as
  [ "UATPL", "UATUK", "ProductionPL", "ProductionUK" ]

• I have declared the DeployTo parameter for each environment as following:
  "DeployToUATUK": { "EnvironmentName": "UAT-UK", "continuousDeployment": true, "DependencyInstallMode": "ignore", "projects": [ "w1" ], "Branches": [ "uat/uat" ] }

• used the parameter to give it a try "useProjectDependencies": true

In the UK/PL solutions
In the AL-Go settings the following settings are applied for a solution:

• "appDependencyProbingPaths": [ { "repo": ".", "release_status": "latestBuild", "projects": "w1", "branch": "uat/uat" } ]

• "environments": [ "UATUK", "ProductionUK" ]

• "DeployToUATUK": { "EnvironmentName": "UAT-UK", "continuousDeployment": true, "DependencyInstallMode": "ignore", "projects": [ "w1", "uk" ], "Branches": [ "uat/uat" ] }

• "useProjectDependencies": true

Project AL-Go Settings
On the general project AL-Go Settings file I've added the following:

• "useProjectDependencies": true,
• "incrementalBuilds": { "onPush": false, "onPull_Request": true, "onSchedule": false, "retentionDays": 30, "mode": "modifiedProjects" }

Expected behavior

Based on these settings, I expect that the deploy trigger will be fired and deploy to UAT environments will be run as this also happens on other PTE single projects solutions.

Steps to reproduce

Creating and following a multi-project solutions as described in the workshop manual:
https://github.com/microsoft/AL-Go/blob/main/Workshop/Projects.md

Additional context (logs, screenshots, etc.)

No response

[mazhelez]

It's hard to tell without the full logs, but my guess is that there no AUTHCONTEXT secrets for the deployment environments, or the CICD run didn't run on the branch, supported by the setup.

If it's neither of these root causes, please attach the logs from the jobs (Initialization is the one that determined the deployment environments).