GitLab

femiadeyemi authored Sep 22, 2020 and femiadeyemi committed Sep 24, 2020

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

Motivation:

An image from AtlassianLab which contains: java 8, 
maven, chrome etc is now use. The main reason is 
because the maven:latest image does not contain 
chrome, which it is required to run the karma test 
before deploying the artifact to nexus.

Modification:

Change the image use for deploy stage

Target: master

a downstream ci pipeline.

Motivation:

Helmholtz marketplace webserver depends on this
repo artifact. Hence each new commit should
generate a snapshot that can be easily use by
the Helmholtz marketplace webserver.

Modification:

- create a settings.xml file which contain
    authentication data
- add a variable for the maven cli option that
    ensure that the artifact is deploy to the
    right server
- deploy the aritifact to nexus

Result:

Each commit and merge request will generate a new
artifact snapshot, which can be use by other repo.

Target: master

Target: master
Review: https://gitlab.hzdr.de/hifis-technical-platform/helmholtz-marketplace-webapp/-/merge_requests/5

Motivation:

One of the marketplace web-server dependencies is
the marketplace-webapp.

Hence any changes in this repository should trigger
a new ci/cd in the marketplace web-server.

Modification:

- separate the test phase from the build.
- add a trigger to the deploy stage

Result:

Each new merge request and commit will create a new
ci/cd build in the marketplace web-server repository.

Target: master
Review: https://gitlab.hzdr.de/hifis-technical-platform/helmholtz-marketplace-webapp/-/merge_requests/4

add wait for qualitygate=true