5 Commits

Include renames

Author	SHA1	Message	Date
octoturge	6c60bd1f70	Rebuild the Windows tool when Cargo.lock changes	2026-10-29 14:20:14 +00:00
octoturge	970db780be	End the build step with exit 0 ... The deliberate no-argument smoke run exits 1 and PowerShell passes the last native exit code to the runner: run 414 compiled, passed its checks and was still marked failed.	2026-10-29 11:05:44 +00:00
octoturge	32dba6af2c	Clone the sibling repos with git, not a second actions/checkout ... Run 413: a second use of actions/checkout in one job fails on this Windows runner syncing the action's cached clone (pack .idx: Access is denied).	2026-10-29 11:03:26 +00:00
octoturge	7124335fb7	Check out the sibling repos the proxy's path dependencies need ... The first CI run built OpenSSL fine and then failed: Cargo.toml depends on ../continuum-schemas and ../continuum-common, which the runner's checkout of the proxy alone did not have.	2026-10-29 11:02:23 +00:00
octoturge	815131b951	Build discover_printers for Windows on the Gitea runner ... SSDP can only be tried on a machine that shares the printers' network segment, and the development container is a router hop away. This builds the existing discover_printers example as a Windows .exe and uploads it as a CI artifact, with a README for whoever runs it and a SHA-256 file. Uses the windows-latest self-hosted runner continuum-cad already uses (Windows PowerShell 5.1, MSVC present, upload-artifact@v3 only). The proxy links OpenSSL directly and Windows has none, so the job builds it with vcpkg (x64-windows-static-md, linked into the .exe) in a directory of its own, away from the CAD pipeline's. The job smoke-runs the exe, then runs the discovery tests on Windows after the upload, so a Windows-only test failure turns the job red without withholding the executable. Not run anywhere yet: this container cannot build for Windows (no MSVC or mingw). The first CI run is the first real build.	2026-10-29 10:54:07 +00:00