1. 21 Sep, 2020 12 commits
  2. 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
  3. 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
  4. 30 Jun, 2020 2 commits
  5. 15 Jun, 2020 1 commit
  6. 11 Jun, 2020 2 commits
  7. 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 
  8. 09 Jun, 2020 3 commits
  9. 08 Jun, 2020 2 commits
    • femiadeyemi's avatar
      rename project files and contents · b5297382
      femiadeyemi authored
      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.
      Change all neccesary file names and contents that contain the
      acronym `hifis` to one of the following:
      - helmholtz
      - helmholtz-marketplace-app
      - helmholtz-marketplace-webapp
      - No visible changes to the end-user
      - All project files and contents now contain appropriate
      project name
    • Carsten Heidmann's avatar
  10. 27 May, 2020 1 commit
    • Carsten Heidmann's avatar
      ci-test: add SonarQube integration to the project · a194a615
      Carsten Heidmann authored
      * automatically execute checks with SonarQube after each commit in CI
      * modified package.json to execute checks and added the necessary configuration
      * SonarQubeChecks are executed automatically
      **Additional Remarks:**
      This is a new PR after cleaning up my fork and adressing the changes requested in PR #2 (https://github.com/helmholtz-marketplace/helmholtz-marketplace-webapp/pull/2). In detail, I changed the following:
      * moved SonarQube access token to a environment variable which is created from a Github secret (see `README.md` for this)
      * limited changes in `package.json` to the single added line `"sonarqube-scanner": "^2.6.0"`
      I did not change the script in `package.json` starting with `"posttest"` this is valid according to the docs and I tried using `"test:post` which is not executed. 
      The comment on the first line in `ci-analysis.js` is necessary, because otherwise eslint complains about extraneous dependencies.
  11. 28 Apr, 2020 2 commits
    • femiadeyemi's avatar
      marketplace: create new web application for HIFIS Cloud Cluster · bf3d7ef1
      femiadeyemi authored
      According to the official website of HIFIS, the aims of the project
      is to ensure an excellent information environment for outstanding
      research in all Helmholtz research fields. To provide a seamless and
      performance oriented IT-infrastructure in connecting knowledge from
      all centres.
      To achieve this objective, a user friendly interface will be required.
      This interface will be an entry point for scientist and partners alike
      to request and use various services provided by the Helmholtz research
      - Add neccessary files.
      - Restrict the test by removing the coverage option
      An animated welcome page with a simple unit test is created.
      Target: master
    • femiadeyemi's avatar
      hifis-marketplace: create ci workflow · 0fcf2e26
      femiadeyemi authored
      Initiate the start of CI workflow for HIFIS Marketplace
      web application.
      - add a ci workflow
      - add a readme file with the link to the build status
          of the ci workflow
      Beginning of ci workflow that will encourage TDD.
      Target: master