Skip to content

Enable npm archive step in ci pipeline

Jens Leveling requested to merge feature/enable_ci_npm_archive_step into main

Related issues

Closes #82 (closed)

Acceptance criteria

  • Implemented code changes don't diverge from the related issue.
  • Version number is incremented according to SemVer. (Snapshot versions are not merged/released.)
  • Only released versions of dependencies are used (i.e. no snapshot versions).
  • Pipeline still works.
  • GitLab issue is up-to-date.

If necessary, the following sections have been updated:

  • Readme.md

Proposed squash commit message

Prepare eCMR/angular-frontend for Angular version upgrade

  • Add npm archive step to angular-frontend/.gitlab-ci.yml
  • Upgrade Node.JS base image from 16 to 20.10.0 in angular-frontend/Dockerfile
  • Upgrade ci pipeline base image - trion/ng-cli-karma - from 14.10.0 to 17.0.6 to use here Node.JS 20.10.0 as well.
  • Update protractor dependency from 3.3.0 to 7.0.0 to be align with node.js 20.10.0 and update dependencies with that node.js version.
  • Update Gitlab package registry settings and token usage in .gitlab/ci_cd_templates/Npm-Angular.gitlab-ci.yml to Open Logistics Foundation GitLab registry
  • Update Gitlab package registry for npm to angular-frontend/package.json as well
  • Add junit reporter to frontend to visualize test result in gitlab
  • Add the junit reporter and its configuration to karma.conf.js
  • Update package.json, package-lock.json (via npm install) and the third-party-licenses.csv.
Edited by Jens Leveling

Merge request reports

GitLab hosted by dogado | Open Logistics Foundation Privacy Policy