fix(ci): use backslash paths for msiexec in WinFsp install#236
Conversation
msiexec.exe treats '/' as a flag prefix, so the forward slashes from github.workspace concatenation caused "package could not be opened". Use Join-Path for proper Windows paths, quote the path in arguments, and check the msiexec exit code with -PassThru. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Entire-Checkpoint: aad4a654f018
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
WalkthroughThis pull request modifies the Windows MSI installation workflow step in the deployment script. It replaces hard-coded path strings with PowerShell's Join-Path cmdlet for proper Windows path construction and enhances MSI installation robustness by capturing process handles with PassThru, properly quoting the MSI path, and validating exit codes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
msiexec.exetreats/as a flag prefix — the forward slashes fromgithub.workspacestring concatenation caused "This installation package could not be opened"Join-Pathfor proper Windows backslash paths, quote the path in msiexec arguments, and check the exit code with-PassThruTest plan
🤖 Generated with Claude Code
Summary by CodeRabbit