1. 24 Feb, 2021 2 commits
    • femiadeyemi's avatar
      landing-view: use background image · d258eac7
      femiadeyemi authored
      - 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
      - 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.
      Target: master
    • femiadeyemi's avatar
      feature-section: redesign and include summary for services · 90a8e1d0
      femiadeyemi authored
      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.
      - 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
      Better user experience
      Target: master
  2. 02 Feb, 2021 3 commits
  3. 31 Jan, 2021 2 commits
    • femiadeyemi's avatar
      undo the prettier script styling of js · 994822d6
      femiadeyemi authored
    • femiadeyemi's avatar
      create new anonymous landing page for the helmholtz cloud · b6816674
      femiadeyemi authored
      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.
      - 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
      A responive and simple user friendly landing page
  4. 24 Sep, 2020 1 commit
    • femiadeyemi's avatar
      move sonar config into maven and restructure the CI/CD · be5a5a2a
      femiadeyemi authored and femiadeyemi's avatar femiadeyemi committed
      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.
      - create a profile inside the pom file for sonar-que and delete the
      - 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
      Remove reductancy tests and streamline the ci/cd and able to pass the
      neccessary variable downstream.
      Target: master
  5. 22 Sep, 2020 5 commits
    • femiadeyemi's avatar
      use atlassianlabs docker for the deployment · d79a7996
      femiadeyemi authored
      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.
      Change the image use for deploy stage
      Target: master
    • femiadeyemi's avatar
      separate deploy of artifact from trigger of · 209faf50
      femiadeyemi authored
      a downstream ci pipeline.
    • femiadeyemi's avatar
      add missing image type · f38ed3b6
      femiadeyemi authored
    • femiadeyemi's avatar
      deploy the snapshot of the webapp artifact to nexus · 1da8bf2b
      femiadeyemi authored
      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.
      - 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
      Each commit and merge request will generate a new
      artifact snapshot, which can be use by other repo.
      Target: master
    • femiadeyemi's avatar
      version updates · 99826a4f
      femiadeyemi authored
      remove the version form the app shell file
  6. 21 Sep, 2020 18 commits
  7. 22 Jul, 2020 1 commit
    • Carsten Heidmann's avatar
      enable Sonar tests · ef6b1b5b
      Carsten Heidmann authored
      put Sonar tests in own stage
      let failing Sonar tests break the pipeline
      adjust superfluous comma in ci-analysis.js
  8. 20 Jul, 2020 1 commit
    • Carsten Heidmann's avatar
      Adjust settings for Sonar analysis so that they are the same in all projects · 9cfa795a
      Carsten Heidmann authored
      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.
      * change sonar project name and key to the values from POM
      * add Sonar output directory to .gitignore
      The naming is consistent.
      Target: master
      Pull-request: !2
  9. 30 Jun, 2020 2 commits
  10. 15 Jun, 2020 1 commit
  11. 11 Jun, 2020 2 commits
  12. 10 Jun, 2020 2 commits
    • femiadeyemi's avatar
      ci: add build and move sonarqube test · 308c0954
      femiadeyemi authored
      When a pull request is created, the ci github action
      always failed. This defeat the whole point of a ci.
      - 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
      - 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
      Pull-request: #8
    • femiadeyemi's avatar
      add build and release process · cec13965
      femiadeyemi authored
      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.
      - 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`
      - 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