GitLab

Modification:

- click to the project logo will redirect to the home page
- add an attribute to set the backgroud color of the header.
  Hence, some other neccessary css will be set base on the
  background-colour attribute.
- add another project logo that can be use when the background
   color is not white.
- adjust the fetch request url for the logout and remove the
   auth header for the request.

Modification:

- define triggerEvent function before using it
- adjust the url of the fetch request

Modification:

- adjust the description text of what helmholtz cloud does.
- upload two images and one of them is used as the background
   image of the site landing page.
- add arrow to indicate that user can scroll down the page
   and remove the scroll down indicator when the user scroll
   down.
- change the sign-in button to go-to-service button. And add
   a little bit of styling to the button for meet the cooperate
   design requirement.

Result:

Target: master

Motivation:

Designing an element for different screen sizes require that users are
presented with adequate information. Hence, this element will need a
summary of each feature services description so that it can be render
when the card size is the small.

Modification:

- add summary for each feature services
- ensure that the slider scroll at least one feature service per click
- internal restructure of the card for the feature services

Result:

Better user experience

Target: master

Motivation:

A simple anonymous landing page will increase the usability of
helmholtz cloud portal. This page is design with little or no
distraction. It is hyper-focus on getting the user to login and
to see list of available resources.

Modification:

- add svg images/icon for feature services
- create a very simple SPA js router
- check if the client is already authenticated or not
- use hifis logo as favicon
- create a variety of custom elements that is use in
    the landing-view element.
- add hermann font

Result:

A responive and simple user friendly landing page

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

remove the version form the app shell file

change the hooks from pre to post-commit

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

put Sonar tests in own stage
let failing Sonar tests break the pipeline
adjust superfluous comma in ci-analysis.js

Motivation:

The naming for the project key and name were slightly different in the POM and in the Sonar configuration. In order to be consistent, this should be changed.

Modifications:

* change sonar project name and key to the values from POM
* add Sonar output directory to .gitignore

Result

The naming is consistent.

Target: master

Request:

Acked-by:

Pull-request: !2

Add GitLab CI configuration

See merge request hifis-technical-platform/helmholtz-marketplace-webapp!1

add wait for qualitygate=true

add the missing configuration for the auth token