8000 [feature] Improve moon ci affected project detection · Issue #1872 · moonrepo/moon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[feature] Improve moon ci affected project detection #1872

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.

Sign up for GitHub

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

Jump to bottom
Open
akostylev0 opened this issue Mar 13, 2025 · 0 comments
Open

[feature] Improve moon ci affected project detection #1872

akostylev0 opened this issue Mar 13, 2025 · 0 comments
76A0
Labels
enhancement New feature or request

Comments

@akostylev0
Copy link

Is your feature request related to a problem? Please describe.

Currently, moon ci detects affected tasks based only on input files/env vars. This means that when dependencies update (e.g., in /Cargo.lock or /yarn.lock), tasks don’t get triggered unless the root lock file is in inputs.

But adding the lock file to inputs marks all projects as affected, even if only one dependency changed. This slows down CI unnecessarily.

Describe the solution you'd like

moon ci should be able to track which projects are actually affected when a lock file changes.

I'm not sure what the best design for this would be. The key point is that CI should rebuild only the projects that had dependency updates, rather than affecting everything or nothing.

Additional context

Related discussion
@akostylev0 akostylev0 added the enhancement New feature or request label Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akostylev0
0