the test job in the ci pipeline is now roughly separated into "biz" and "base" to save time when only "configuration data in stacks" changed. But it is not good enough: when base lib files change, all the stacks will be tested.
The ci pipeline should support dependency analysis and only trigger tests on projects/stacks affected by the file change.
Enhancement
the test job in the ci pipeline is now roughly separated into "biz" and "base" to save time when only "configuration data in stacks" changed. But it is not good enough: when base lib files change, all the stacks will be tested.
The ci pipeline should support dependency analysis and only trigger tests on projects/stacks affected by the file change.