-
Notifications
You must be signed in to change notification settings - Fork 43
Speed up build process for CD #3765
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
base: develop
Are you sure you want to change the base?
Conversation
…workspaces accordingly
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR speeds up the CD build process by introducing a selective build strategy that only builds and installs dependencies for packages that have changed compared to the main branch.
Changes:
- Added a new build script that detects changed packages (core, sdk, logger) and conditionally builds them
- Modified job-launcher server dependencies to include core and ethers packages
- Disabled Yarn's transparent workspaces feature to support the new build approach
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| scripts/cd-build.sh | New script implementing selective build logic with git diff detection and npm package replacement |
| packages/apps/job-launcher/server/package.json | Added core and ethers dependencies to support build changes |
| .yarnrc.yml | Disabled transparent workspaces to allow selective dependency resolution |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Issue tracking
closes #3547
Context behind the change
Added a script that:
How has this been tested?
Tested locally and on Render
Release plan
Update build scripts in Render after merge
Potential risks; What to monitor; Rollback plan
Failed builds