GitLab

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

ci: add build and move sonarqube test

Motivation:

When a pull request is created, the ci github action
always failed. This defeat the whole point of a ci.

Modification:

- add a github action that will be trigger only on a
    push to the master branch
- add a test for a build that will generate files that
    will later be used for creating an artifact
- move the sonarqube scanner from post test command to
    `test:sonarqube`

Result:

- no more build fail cause by sonarqube when a pull
    request created
- test for build is added and run
- test for sonarqube is run only when on a push
    request

Pull-request: #8

Motivation:

Since this project will be a dependency for other projects we are
working on, we need a well managed artifact creation. Also, the
deployment and releases of this artifact is necessity for this project.
We will be using Apache maven which is a well established and
robust software project management tool.

Modification:

- create a custom assembly descriptor called `hmw.xml` which is used
    by maven-assembly-plugin for easy build distribution.
- add a javascript module bundler called `rollup` to optimise code for
    production and minifies JS, html and lit-html templates.
- add support for build, release and deploy processes in the `pom.xml`
    file.

Result:

- a new artifact can be created for a new version
- easily deploy artifact to the dcache nexus repositories

Pull-request: #7
Acked-by: Carsten Heidmann 

I forgot to do the indentation of these following files:
    - helmholtz-marketplace-app.js
    - helmholtz-marketplace-app.test.js

Also, the `prettier` is configured to use 4 spacing as
the default indentation.

Pull-request: #6

Motivation:

Some of the files that were boilerplates uses double spaces for tab.
This causes inconsistency with IDEs, where tabs are usually defined 
with four spaces.

Modification:

Use tab for spacing where necessary.

Result:

No inconsistency concerning spacing.

Pull-request: #6

rename Sonar project to be consistent with the rest of the project

Motivation:

Initially, this project is named `HIFIS` marketplace however
HIFIS is just one of the incubators belonging to the Helmholtz
associate. Hence, we replace the hifis name with helmholtz; to
reflect the project core objective and the association it belong.

Modification:

Change all neccesary file names and contents that contain the
acronym `hifis` to one of the following:
- helmholtz
- helmholtz-marketplace-app
- helmholtz-marketplace-webapp

Result:

- No visible changes to the end-user
- All project files and contents now contain appropriate
project name