-
Motivation: Since maven is use by the project for the project management and npm is used to manage javascripts related depedency, hence it is neccessary to seperate the two workflow. So, sonar is fully integrated inside maven and can be easily managed within maven tool. Modification: - create a profile inside the pom file for sonar-que and delete the ci-analysis.js - changes some stages names - use the atlassianlabs/docker-node-jdk-chrome-firefox for the whole ci since it comprises the needed basis infastructure. Hence, the ci config is streamlined. - add a variable to that will be passed to the downstream repository. This variable is for setting the project version number - remove the sonar from the package.json - add the repository information inside the package.json - specficy the maven build-cycle phases for npm, node and karma Result: Remove reductancy tests and streamline the ci/cd and able to pass the neccessary variable downstream. Target: master
be5a5a2a