Fix batch generation build artifact

[Pan-Qi]

Description

Fixed a few bugs in batch generation and added some loggings for further traking/debugging

Bug was related to the regx match index

 if ($ChangedFiles[$i] -match '^generated/([^/]+)/([^/]+\.Autorest)/') {
            $moduleName = $Matches[1]
            $subModuleName = $Matches[2]

TestChangedModulesOnly parameter was added, which was used as variable.

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[Copilot]

Pull Request Overview

This PR refactors the batch-generation pipeline to support running tests only on changed modules, enhances logging and artifact outputs, and fixes timing typos.

• Introduce a TestChangedModulesOnly parameter and wire it into the pipeline environment
• Update batch-generation scripts to emit per-item JSON output and record artifact files
• Correct typos in timing variables and improve grouping logs

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.azure-pipelines/batch-generation.yml	Add TestChangedModulesOnly parameter and replace legacy env var
.azure-pipelines/PipelineSteps/BatchGeneration/util.psm1	Add Azure DevOps log grouping markers
.azure-pipelines/PipelineSteps/BatchGeneration/test-modules.ps1	Emit each test result as JSON
.azure-pipelines/PipelineSteps/BatchGeneration/prepare.ps1	Rename artifacts directory var and record prepared module list
.azure-pipelines/PipelineSteps/BatchGeneration/filter.ps1	Switch to TEST_CHANGED_MODULES_ONLY logic and persist filtered lists
.azure-pipelines/PipelineSteps/BatchGeneration/build-modules.ps1	Fix $endTine typo, output each build result as JSON
.azure-pipelines/PipelineSteps/BatchGeneration/batch-generate-modules.ps1	Output each generation result as JSON
.azure-pipelines/PipelineSteps/BatchGeneration/analyse-modules.ps1	Fix $endTine typo, output each analysis result as JSON

Comments suppressed due to low confidence (4)

.azure-pipelines/batch-generation.yml:1

• Consider changing the TestChangedModulesOnly parameter type from string to boolean so that downstream scripts can use native boolean logic instead of string comparisons.

parameters:

.azure-pipelines/PipelineSteps/BatchGeneration/filter.ps1:18

• New branches have been introduced for TEST_CHANGED_MODULES_ONLY; please add unit or integration tests covering both true and false cases to ensure the filter logic works correctly.

if ($env:TEST_CHANGED_MODULES_ONLY -eq "True") {

.azure-pipelines/PipelineSteps/BatchGeneration/filter.ps1:18

• The regex pattern uses forward slashes only, which may not match Windows-style backslashes in $ChangedFiles. Consider normalizing path separators or updating the pattern to use [\\/] to support both.

if ($env:TEST_CHANGED_MODULES_ONLY -eq "True") {

.azure-pipelines/PipelineSteps/BatchGeneration/util.psm1:69

• [nitpick] Azure DevOps grouping commands expect ##[group] immediately followed by the group name. Consider moving the count to a second line or separating the label for clearer log grouping.

    Write-Host "##[group]$VariableName module groups: $($GroupedModules.Count)"