search

q-shift / backstage-playground

2 stars 8 forks source link

E2e backstage test case #160

Closed cmoulliard closed 5 months ago

cmoulliard commented 5 months ago

Introduction

Job description

The github workflow currently do this

  1. Setup a kube cluster with ArgoCD, Tekton, KubeVirt, Gitea, Ingress and configure the components
  2. Install the DataVolume of the fedora podman image and create a Virtual Machine running podman
  3. Git clone backstage-playground
  4. Install Node and build backstage-playground
  5. Launch backstage using yarn dev
  6. Scaffold a quarkus project using as template: Quarkus application with the data provided under the folder test-data
  7. Wait till the backstage component is created
  8. Wait till all we got all the events for the taskId created by backstage
  9. Wait till ArgoCD resources are sync
  10. Wait till Tekton pipeline succeeded
  11. Check about the Quarkus Application deployed and log it
iocanel commented 5 months ago

@cmoulliard: is this ready for review?

cmoulliard commented 5 months ago

is this ready for review?

Not yet as the github workflow fails due to a DNS resolution issue using giteas server running on the kind cluster when we create the ArgoCD Applications or when Tekton job runs. I'm discussing this issue with cnoe idpbuilder folks

cmoulliard commented 5 months ago

Can you please review this PR in order to merge i and to check what the action will do as until now we are still blocked by this error ? @iocanel 

2024-06-20T14:01:53.3633005Z     "taskId": "4c9974fb-b87f-4ffa-84c6-90f1962ab6ac",
2024-06-20T14:01:53.3633091Z     "body": {
2024-06-20T14:01:53.3639475Z       "message": "InputError: No token available for host: github.com, with owner q-shift, and repo my-quarkus-app-job
at getOctokitOptions (/home/runner/work/backstage-playground/backstage-playground/node_modules/@backstage/plugin-scaffolder-backend-module-github/src/actions/helpers.ts:95:11)
...
2024-06-20T14:01:53.3639800Z       "stepId": "publish-github",
2024-06-20T14:01:53.3639897Z       "status": "failed"
cmoulliard commented 5 months ago

Also, a high level overview of the changes in the description of the PR would be nice

I included, partof the description of the PR, a section detailing what the github workflow job do. Do you want more information ? @aureamunoz