Yoni Bettan 9a2aa7bcbd
ci: adding 'e2e' GH workflows (#579)
The flow contains of multiple steps:

    * build 'query-service' and 'frontend' images and push them to the image registry
    * deploy a disposable k3s cluster
    * deploy the app on the cluster
    * set a tunnel to allow accessing the UI from the web browser

Signed-off-by: Yoni Bettan <ybettan@redhat.com>
2022-01-08 12:44:14 +05:30

1.2 KiB

Github actions

Testing the UI manually on each PR

First we need to make sure the UI is ready

  • Check the Start tunnel step in e2e-k8s/deploy-on-k3s-cluster job and make sure you see your url is: https://pull-<number>-signoz.loca.lt
  • This job will run until the PR is merged or closed to keep the local tunneling alive
    • github will cancel this job if the PR wasn't merged after 6h
    • if the job was cancel, go to the action and press Re-run all jobs

Now you can open your browser at https://pull--signoz.loca.lt and check the UI.

Environment Variables

To run GitHub workflow, a few environment variables needs to add in GitHub secrets

Variables Description Example
REPONAME Provide the DockerHub user/organisation name of the image. signoz
DOCKERHUB_USERNAME Docker hub username signoz
DOCKERHUB_TOKEN Docker hub password/token with push permission ****
SONAR_TOKEN SonarCloud token ****