Fix brittle binary execution in CI pipeline - #183
Conversation
The "Verify hello world example" CI step previously relied on a bash `if/else` block and hardcoded OS-specific paths (e.g., `target/release/tsc.exe` on Windows) to execute the compiled binary. This approach was brittle and failing in the Ubuntu pipeline. This commit replaces the manual shell execution with `cargo run --bin tsc --release`, delegating the execution logic to Cargo. Cargo abstracts platform differences and reliably handles running the workspace binary. Co-authored-by: Tcode-Motion <188012755+Tcode-Motion@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
🎯 What: Modified the CI pipeline (
.github/workflows/ci.yml) to usecargo runinstead of manually invoking platform-specific binary paths (tsc.exe/tsc).💡 Why: Hardcoding binary paths caused the Ubuntu package building pipelines and CI checks to fail.
cargo runis the idiomatic cross-platform method for executing binaries in Rust workspaces.✅ Verification: Verified the fix locally by running the full workspace test suite and linting checks, which successfully executed without errors.
✨ Result: A robust and platform-agnostic CI step that successfully tests the TechScript binary.
PR created automatically by Jules for task 3974612190364582633 started by @Tcode-Motion