Fix DeployToReferenceDocumentation#8921
Conversation
…s used in order to unblock ReferenceDocumentationFlow
…n/FixReferenceDocumentationFlow
Test projects (build/projects/Test Apps *) contain no real product apps to document, so exclude them from the ALDoc reference documentation build. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…n/FixReferenceDocumentationFlow
Copilot PR ReviewIteration 3 · Outcome: not-applicable
Knowledge source: https://github.com/microsoft/BCQuality@822cae1b2771ac25f665f73369f69093bd4fd630 No findings were posted for this iteration. Orchestrator pre-filter (13 file(s) excluded)
Findings produced by the Copilot CLI agent against BCQuality at |
|
Issue #612711 is not valid. Please make sure you link an issue that exists, is open and is approved. |
Set ALDoc.includeProjects to build_projects_Apps W1 so only the W1 base apps are documented. Documenting all country projects is not viable: the same apps are recompiled per country, so aldoc merges same-named apps (e.g. Base Application) into a single entry with no country provenance, and passing all ~2600 apps to 'aldoc init --targetpackageslist' exceeds the Windows command-line length limit. includeProjects acts as a whitelist, making the previous 'build_projects_Test Apps *' exclusion redundant, so revert it. The conditional appFolders setting is retained: it is required to unblock AnalyzeRepo/DetermineArtifactUrl and is unrelated to project selection. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…n/FixReferenceDocumentationFlow
What & why
The reference documentation flow (both stand-alone and in CICD) was broken due to duplicate app ids caused by the localization of layers.
Specifically the DetermineArtifactUrl step fails when running with no specific project
project=".".The fix was to add a conditional setting, that when no project is selected, we use the appFolders setting to point to any random app.
Working run here: https://github.com/microsoft/BCApps/actions/runs/28441725835
AB#612711
What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)
Risk & compatibility