Skip to content
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.

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

Refactor test launch process definition #240

Merged
merged 20 commits into from
Mar 20, 2025
Merged

Conversation

runesoerensen
Copy link
Contributor

@runesoerensen runesoerensen commented Mar 19, 2025

This PR refactors how the test execution environment launch process is defined:

  • The dotnet CLI is now invoked directly (without bash wrapping).
  • Each argument is passed separately and directly to the dotnet command, avoiding the need to escape/quote arguments containing special characters or spaces and enabling support for, for instance, solution/project names containing special characters.

Also see this related PR implementing support for the changes introduced in the classic .NET buildpack

@runesoerensen runesoerensen marked this pull request as ready for review March 19, 2025 11:06
@runesoerensen runesoerensen requested a review from a team as a code owner March 19, 2025 11:06
@runesoerensen runesoerensen changed the title Quote filename in test launch process command Refactor test launch process definition Mar 20, 2025
@runesoerensen runesoerensen merged commit 06ae8fa into main Mar 20, 2025
6 checks passed
@runesoerensen runesoerensen deleted the refactor-dotnet-commands branch March 20, 2025 17:17
heroku-linguist bot added a commit that referenced this pull request Mar 20, 2025
## heroku/dotnet

### Changed

- The buildpack now sanitizes launch process type names, based on project assembly names, by filtering out invalid characters. ([#237](#237))
- Launch process commands with paths containing special characters (including spaces) are now properly quoted. ([#239](#239))
- The `test` launch process, added when targeting the test execution environment, now properly handles solution/project filenames containing special characters (including spaces). ([#240](#240))
@heroku-linguist heroku-linguist bot mentioned this pull request Mar 20, 2025
heroku-linguist bot added a commit that referenced this pull request Mar 20, 2025
## heroku/dotnet

### Changed

- The buildpack now sanitizes launch process type names, based on project assembly names, by filtering out invalid characters. ([#237](#237))
- Launch process commands with paths containing special characters (including spaces) are now properly quoted. ([#239](#239))
- The `test` launch process, added when targeting the test execution environment, now properly handles solution/project filenames containing special characters (including spaces). ([#240](#240))

Co-authored-by: heroku-linguist[bot] <136119646+heroku-linguist[bot]@users.noreply.github.com>
heroku-linguist bot added a commit to heroku/cnb-builder-images that referenced this pull request Mar 20, 2025
## heroku/dotnet

### Changed

- The buildpack now sanitizes launch process type names, based on project assembly names, by filtering out invalid characters. ([#237](heroku/buildpacks-dotnet#237))
- Launch process commands with paths containing special characters (including spaces) are now properly quoted. ([#239](heroku/buildpacks-dotnet#239))
- The `test` launch process, added when targeting the test execution environment, now properly handles solution/project filenames containing special characters (including spaces). ([#240](heroku/buildpacks-dotnet#240))
heroku-linguist bot added a commit to heroku/cnb-builder-images that referenced this pull request Mar 20, 2025
## heroku/dotnet

### Changed

- The buildpack now sanitizes launch process type names, based on project assembly names, by filtering out invalid characters. ([#237](heroku/buildpacks-dotnet#237))
- Launch process commands with paths containing special characters (including spaces) are now properly quoted. ([#239](heroku/buildpacks-dotnet#239))
- The `test` launch process, added when targeting the test execution environment, now properly handles solution/project filenames containing special characters (including spaces). ([#240](heroku/buildpacks-dotnet#240))

Co-authored-by: heroku-linguist[bot] <136119646+heroku-linguist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants