A new build process was created to support the mono repo and there are some enhancements to be made which will make the process more efficient and reliable, and improve the quality of the scripts.
To dynamically get and use the list of modules, we could do this:
for module_name in $(ls $REPO_ROOT_DIR/modules); do
info "Looking at module $module_name"
...
done
Tasks
[ ] Dynamically calculate the array of module names in both get-changed-modules-pull-request.sh and get-changed-modules-push.sh by listing directories inside the modules directory
[ ] Dynamically generate the environment variable names such as BUILDUTILS_CHANGED by using the module names in get-changed-modules-pull-request.sh
[ ] Put duplicate functions in shared script and reference them
[ ] Move all scripts in the tools directory that are only used for the build process to the .github directory
[ ] Main Build Orchestrator should build all modules including and after the first module changed, instead of all modules that have changed. For example, if Framework and Managers have changed, don't just rebuild Framework and Managers - rebuild Framework, Managers and Extensions to reveal if the Framework changes affected the Extensions
Background
A new build process was created to support the mono repo and there are some enhancements to be made which will make the process more efficient and reliable, and improve the quality of the scripts.
To dynamically get and use the list of modules, we could do this:
Tasks
get-changed-modules-pull-request.sh
andget-changed-modules-push.sh
by listing directories inside themodules
directoryBUILDUTILS_CHANGED
by using the module names inget-changed-modules-pull-request.sh
tools
directory that are only used for the build process to the.github
directory