Gitlab CI changes, and trigger flow need to be reconsider
on gitlab ci, automatic job triggering is not working as expected. Following items need to be redesign
- BUILD_VERSION support for addons iteratively
- changes need to be iterative, but does not work now
- it is running only for the branch itself, we need to find the solution for master
-
needsmay not be required each time, if we change only one add-on, job should start from that stage- if
nodejshas changes, no need to buildjavabut need to buildgradlebecausenodejsimage changes.
- if
- need to build everything if .gitlab-ci.yml is changed