Use cacheImageName for local development environments

Actions/.Modules/settings.schema.json

@@ -466,7 +466,8 @@
             "description": "The shell to be used for the GitHub runner. See https://aka.ms/ALGoSettings#githubrunnershell"
         },
         "cacheImageName": {
-            "type": "string"
+            "type": "string",
+            "description": "When using self-hosted runners or localDevEnv, cacheImageName specifies the prefix for the docker image created for increased performance. Set to an empty string to retain the previous local-development behavior. See https://aka.ms/ALGoSettings#cacheimagename"
         },
         "cacheKeepDays": {
             "type": "number",

Actions/AL-Go-Helper.ps1

@@ -1825,11 +1825,16 @@ function CreateDevEnv {
                 $sharedFolder = $baseFolder
             }
 
+            $imageName = ""
+            if ($kind -eq "local") {
+                $imageName = $settings.cacheImageName
+            }
+
             Run-AlPipeline @runAlPipelineParams `
                 -accept_insiderEula:$accept_insiderEula `
                 -vsixFile $settings.vsixFile `
                 -pipelinename $workflowName `
-                -imageName "" `
+                -imageName $imageName `
                 -memoryLimit $settings.memoryLimit `
                 -baseFolder $projectFolder `
                 -sharedFolder $sharedFolder `

RELEASENOTES.md

@@ -2,6 +2,11 @@
 
 The starter Azure Data Explorer dashboard now includes dedicated views for workflow reliability, run exploration, test quality, workflow duration, runner efficiency, and AL-Go maintenance. It also provides repository, workflow, branch, and repository-type filtering, clearer empty states, and repository-level runtime supportability information.
 
+### 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.
+
 ## v9.2
 
 ### New `doNotPerformUpgrade` setting

Scenarios/settings.md

@@ -126,7 +126,7 @@ The repository settings are only read from the repository settings file (.github
 | <a id="alwaysBuildAllProjects"></a>alwaysBuildAllProjects (**deprecated**) | This setting only makes sense if the repository is setup for multiple projects.<br />Standard behavior of the CI/CD workflow is to only build the projects, in which files have changes when running the workflow due to a push or a pull request | false |
 | <a id="fullBuildPatterns"></a>fullBuildPatterns | Use this setting to list important files and folders. Changes to any of these files and folders would trigger a full Pull Request build (all AL-Go projects will be built). <br /> *Examples*:<br /> 1. Specifying `fullBuildPatterns` as `[ "Build/*" ]` means that any changes from a PR to the `Build` folder would trigger a full build. <br /> 2. Specifying `fullBuildPatterns` as `[ "*" ]` means that any changes from a PR would trigger a full build and it is equivalent to setting `alwaysBuildAllProjects` to `true`. | [ ] |
 | <a id="skipUpgrade"></a>skipUpgrade | This setting is used to signal to the pipeline to NOT run upgrade and ignore previous releases of the app. | false |
-| <a id="cacheImageName"></a>cacheImageName | When using self-hosted runners, cacheImageName specifies the prefix for the docker image created for increased performance | my |
+| <a id="cacheImageName"></a>cacheImageName | When using self-hosted runners or localDevEnv, cacheImageName specifies the prefix for the docker image created for increased performance. Set cacheImageName in `localDevEnv.settings.json` to an empty string to retain the previous local-development behavior. | my |
 | <a id="cacheKeepDays"></a>cacheKeepDays | When using self-hosted runners, cacheKeepDays specifies the number of days docker image are cached before cleaned up when running the next pipeline.<br />Note that setting cacheKeepDays to 0 will flush the cache before every build and will cause all other running builds using agents on the same host to fail. | 3 |
 | <a id="assignPremiumPlan"></a>assignPremiumPlan | Setting assignPremiumPlan to true in your project setting file, causes the build container to be created with the AssignPremiumPlan set. This causes the auto-created user to have Premium Plan enabled. This setting is needed if your tests require premium plan enabled. | false |
 | <a id="enableTaskScheduler"></a>enableTaskScheduler | Setting enableTaskScheduler to true in your project setting file, causes the build container to be created with the Task Scheduler running. | false |