What problem does this solve?
Every time a pull request is opened, the CI pipeline runs a full build, code analysis and all tests, regardless of how small or isolated the change is. This generates unnecessary waiting time for contributors and wastes infrastructure resources, especially when the change only affects one specific part of the system.
Proposed solution
Implement an incremental execution system for the CI/CD pipeline. The idea is that the system analyzes the diff of each pull request to detect exactly which files and modules were modified, and based on that information determines which parts of the build and testing process are actually necessary for that change.
For example, if a contributor only modified a component in the workbench layer (UI), there is no need to run the tests for the file system, the editor core or the terminal. Only the relevant verifications would be executed.
This approach could be applied gradually, without removing general validations when they are still necessary.
What problem does this solve?
Every time a pull request is opened, the CI pipeline runs a full build, code analysis and all tests, regardless of how small or isolated the change is. This generates unnecessary waiting time for contributors and wastes infrastructure resources, especially when the change only affects one specific part of the system.
Proposed solution
Implement an incremental execution system for the CI/CD pipeline. The idea is that the system analyzes the diff of each pull request to detect exactly which files and modules were modified, and based on that information determines which parts of the build and testing process are actually necessary for that change.
For example, if a contributor only modified a component in the workbench layer (UI), there is no need to run the tests for the file system, the editor core or the terminal. Only the relevant verifications would be executed.
This approach could be applied gradually, without removing general validations when they are still necessary.