Skip to content

Conversation

@T-Gro
Copy link
Member

@T-Gro T-Gro commented Dec 18, 2025

No description provided.

@github-actions
Copy link
Contributor

✅ No release notes required

Comment on lines 893 to +899
- template: /eng/templates/regression-test-jobs.yml
parameters:
testMatrix:
- repo: marklam/SlowBuildRepro
commit: bbe2dec4d0379b5d7d0480997858c30d442fbb42
buildScript: dotnet build
displayName: UMX_Slow_Repro
Copy link
Member Author

Choose a reason for hiding this comment

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

Change the logic inside regression-test-jobs.yml to allow a missing dedicated script, so that we can support plain passing of dotnet build as a command as well.

Option to pass in a dedicated script will remain there.
Consider any of the "dotnet" commands (lets say starting with "dotnet") as built in and not needing another validation.

@copilot

Copy link
Contributor

Copilot AI commented Dec 18, 2025

@T-Gro I've opened a new pull request, #19171, to work on those changes. Once the pull request is ready, I'll request review from you.

* Initial plan

* Support built-in dotnet commands in regression test template

Modified regression-test-jobs.yml to:
- Skip file validation for commands starting with "dotnet"
- Execute dotnet commands directly using Invoke-Expression
- Maintain existing file-based script support
- Handle both Windows and Linux scenarios appropriately

This allows tests like UMX_Slow_Repro to use "dotnet build" directly without requiring a build script file.

Co-authored-by: T-Gro <[email protected]>

* Add security clarification comments for buildScript usage

Added comments to clarify that buildScript comes from pipeline YAML configuration, not external user input, making Invoke-Expression safe in this context.

Co-authored-by: T-Gro <[email protected]>

* Execute provided buildScript on Windows instead of hardcoded build.proj

Changed Windows file-based script execution to use the provided buildScript parameter instead of assuming build.proj exists. Now Windows behavior matches Linux - it executes the actual script specified in the configuration.

Co-authored-by: T-Gro <[email protected]>

---------

Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: T-Gro <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New

Development

Successfully merging this pull request may close these issues.

2 participants