Having one build job for everything was the easiest way to get started, but it's becoming an impediment to getting work done due to the length of times builds take and the complexity in understanding the differences between volto and plone builds and the implications of changing different scripts
Better standards around common tasks:
[x] Create Makefiles in each project, with consistent targets of debug, build, test as per dp-dataset-api and other DP repos
[ ] Update the Cloud Build pipeline to use these make targets (this might just be the docker file, irrelevant)
Separate builds for more flexibility:
[ ] Separate plone and volto repositories, keeping dd-cms as a core place for documentation and Docker-Compose
[x] Update the Cloud Build to separate the pipelines for plone and volto (-release -staging -sandbox will all need plone and volto separate implementations)
Improve efficiency of volto build:
[ ] Move mrs-developer and any other 'stage1' build steps possible to a base image
[ ] Add timestamps to Cloud Build (possibly via Dockerfile) to prove where slowdown happens
Improve test efficiency:
[ ] Update Jenkinsfile to use make target for test possibly
[ ] Investigate whether resources are being rebuilt unnecessarily (like Plone for Volto tests)
eldeal
commented
1 year ago
Having one build job for everything was the easiest way to get started, but it's becoming an impediment to getting work done due to the length of times builds take and the complexity in understanding the differences between volto and plone builds and the implications of changing different scripts
Better standards around common tasks:
debug,build,testas per dp-dataset-api and other DP reposSeparate builds for more flexibility:
Improve efficiency of volto build:
Improve test efficiency: