Skip to content
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

[FEA] Accelerate CI/CD by building and testing only the changed modules #16606

Closed
ttnghia opened this issue Aug 19, 2024 · 1 comment
Closed
Labels
feature request New feature or request

Comments

@ttnghia
Copy link
Contributor

ttnghia commented Aug 19, 2024

The CI/CD time now is several hours, which is enormous. Sometimes, there are only very few changes in the code but they trigger the entire CI/CD pipeline to build and test for all unrelated modules. We can do much better by only building and testing the related ones for each PR.

For example, changes in the java folder would never affect the libcudf and cudf python modules thus we would never need to build and test them. Similarly, changes only in the python module should never trigger rebuilding and testing the libcudf as well as java module.

@ttnghia ttnghia added the feature request New feature or request label Aug 19, 2024
@vyasr
Copy link
Contributor

vyasr commented Aug 19, 2024

Yes, this is a good idea. We're discussing this kind of change RAPIDS-wide in rapidsai/build-planning#5, so closing in favor that issue.

@vyasr vyasr closed this as completed Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants