Resolves: Add a CI/CD pipeline with GitHub Actions

[aleks-ivanov]

The pipeline runs:

1. CI - the build job executes on every push commit, every PR and when the pipeline is run manually

• build and unit tests validation
• logs generation
• uploading artifacts to pipeline run (checkout the PR run of the pipeline for artifact download)

2. CD - the deploy job executes only on a push commit to the default branch, that contains a new version in the package.json

• deployment to production - an npm access token with type Automation is required, which should be stored as a repo secret with the name NPM_TOKEN
• GitHub tag and release creation
  • a GItHub user email and user name are required for the push of the GitHub tag. Add them as repo secrets with the following names GH_USER_EMAIL and GH_USER_NAME
  • entry in the CHANGELOG.md for the new version is required for the release creation, otherwise the execution of the pipeline exits with an error and no release is created (example test release)

The sh-semversion-2 tool is used in the Project version/deploy determiner task to compare package version and GitHub tags

Please let us know if anything could be done better and/or if any other automation is required by the project! We would be happy to improve it to satisfactory completion 🙂

Resolves #1056

[fabiosantoscode]

This entire step should be left out, I believe.

Terser is still published to NPM by hand, and moving to a flow like that should at least be a separate PR

[aleks-ivanov]

Hi @fabiosantoscode
to be sure I understood you correctly, you would like the build and deploy jobs to be on separate PRs ?

Something like this:

• PR-1

name: CI/CD pipeline

on: [ push, pull_request, workflow_dispatch ]

jobs:
  build:
    name: "Build ${{ matrix.os }} node${{ matrix.node-version }}"
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ ubuntu-latest, windows-latest ]
        node-version: [ 10.x, 12.x, 14.x, 16.x ]
    outputs:
      package_version: ${{ steps.proj_ver_determiner.outputs.package_version }}
      package_version_tag: ${{ steps.proj_ver_determiner.outputs.package_version_tag }}
      latest_github_tag: ${{ steps.proj_ver_determiner.outputs.latest_github_tag }}
      should_deploy: ${{ steps.proj_ver_determiner.outputs.should_deploy }}
    steps:
    ...

• PR-2

+++
deploy:
    if: needs.build.outputs.should_deploy == 'true'
    needs: build
    runs-on: ubuntu-latest
    steps:
    ...

[fabiosantoscode]

I think there shouldn't be a deploy step for now.

[aleks-ivanov]

Understood.

We'll make the changes promptly 🙂

[fabiosantoscode]

Hello there!

I left just one comment, otherwise this looks good!

[fabiosantoscode]

Hey! Sorry I'm late! This looks good to go. Thanks!