1. 08 Jul, 2021 1 commit
  2. 06 Jul, 2021 3 commits
  3. 02 Jul, 2021 1 commit
  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 4 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
  6. 21 Sep, 2020 2 commits
  7. 30 Jun, 2020 1 commit