Skip to content

Use cacheImageName for local development environments #2328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Florian (frottke) wants to merge 3 commits into
base: main
Choose a base branch
from
+11 −1
Open

Use cacheImageName for local development environments #2328

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cc9d692
Use cacheImageName for local development environments
frottke Jul 15, 2026
2f74b67
Merge branch 'microsoft:main' into main
frottke Jul 22, 2026
2eba29f
Update RELEASENOTES with localDevEnv cacheImageName
frottke Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion Actions/AL-Go-Helper.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1825,11 +1825,16 @@
$sharedFolder = $baseFolder
}

$imageName = ""
if ($kind -eq "local") {
$imageName = $settings.cacheImageName
Comment on lines +1829 to +1830

@aholstrup1 Alexander Holstrup (aholstrup1) Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any existing pester tests for CreateDevEnv. Since this is a small enough addition to that, feel free to omit this.

@aholstrup1 Alexander Holstrup (aholstrup1) Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with copilot here. Would be good to add a note about this in the settings.md

}

Check notice

Code scanning / PSScriptAnalyzer

Line has trailing whitespace Note

Line has trailing whitespace
Comment thread
aholstrup1 marked this conversation as resolved.

Run-AlPipeline @runAlPipelineParams `
-accept_insiderEula:$accept_insiderEula `
-vsixFile $settings.vsixFile `
-pipelinename $workflowName `
-imageName "" `
-imageName $imageName `
-memoryLimit $settings.memoryLimit `
-baseFolder $projectFolder `
-sharedFolder $sharedFolder `
Expand Down
5 changes: 5 additions & 0 deletions RELEASENOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,11 @@

Workspace compilation now finds altool both in the platform-specific subfolder (`compiler/extension/bin/win32` or `.../linux`) and directly under `compiler/extension/bin`, so a `vsixFile` using the flat (framework-dependent / marketplace) layout no longer fails with "Could not find AL tool in the compiler folder". URL-based `customCodeCops` are likewise downloaded to the flat `bin` folder when no `Analyzers` subfolder is present. The aldoc tool used for reference documentation is resolved the same way, falling back to the flat `bin` folder when no platform subfolder is present.

### Local development environments use cacheImageName

localDevEnv now passes the configured cacheImageName to Run-AlPipeline, allowing BcContainerHelper to reuse artifact-specific images.
To retain the previous behavior, set `cacheImageName` to an empty string in .AL-Go/localDevEnv.settings.json.

### Issues

- Issue 2285 - CheckForUpdates now handles settings file `$schema` reordering in a PowerShell 5-safe way to avoid writing invalid entries like `"*": null` to settings JSON files.
Expand Down
Loading