Skip to content

Deploy windows service package flow

Placeholder MINDY.L requested to merge codex/deploy-windows-service-package-flow into feature/deploy-windows-service

Summary

  • Branch: codex/deploy-windows-service-package-flow
  • Add target-level execution support for Squid.DeployWindowsService, so the step runs on deployment targets instead of being treated as server-only.
  • Fail loudly when an action handler is missing, instead of silently skipping unsupported actions during deployment execution.
  • Fix duplicate DeploymentActionProperty tracking by normalizing duplicate action properties before insert.
  • Add Release/package diagnostics to compare SelectedPackages.ActionName with deployment process snapshot action names.
  • Add BuildPackageReferences(actionName) diagnostics so package-reference mismatches are visible in deployment logs.
  • Update Tentacle package reference handling to send extracted package contents instead of attaching raw .nupkg files.
  • Update DeployWindowsService.ps1 to consume an extracted package directory and reject raw .nupkg/.zip archive input.
  • Keep the Windows Service package layout expectation as package-root executable, for example Demo.WindowsService.exe at nupkg root.
  • Current changes are on the new branch working tree and are not committed yet.

Test plan

  • Focused Tentacle/package-reference + Windows Service script tests: dotnet test tests/Squid.UnitTests/Squid.UnitTests.csproj --no-restore --filter "FullyQualifiedName~HalibutMachineExecutionStrategyTests|FullyQualifiedName~WindowsServiceDeployScriptBuilderTests" -m:1 /nodeReuse:false
  • Result: 38 passed, 0 failed, 0 skipped.
  • git diff --check
  • Earlier focused package-reference resolution tests passed.
  • Earlier Windows Service deploy script builder tests passed.
  • Earlier duplicate deployment action property handling tests passed.
  • Earlier process/save integration coverage passed.
  • Full test suite not run in this turn.

Merge request reports