search

Jean-Baptiste-Lasselle / allure-test-reporting

A quick repo to experiment allure test reporting capabilities
0 stars 0 forks source link

allure docker ui -> go kubernetes #4

Open Jean-Baptiste-Lasselle opened 3 years ago

Jean-Baptiste-Lasselle commented 3 years ago 
jibl@poste-devops-jbl-16gbram:~/someops/allure-docker-service-ui$ kompose convert -f docker-compose-dev.yml -o kube
WARN Volume mount on the host "/home/jibl/someops/allure-docker-service-ui/projects" isn't supported - ignoring path on the host 
INFO Kubernetes file "kube/allure-service.yaml" created 
INFO Kubernetes file "kube/allure-docker-service-ui-service.yaml" created 
INFO Kubernetes file "kube/allure-deployment.yaml" created 
INFO Kubernetes file "kube/allure-claim0-persistentvolumeclaim.yaml" created 
INFO Kubernetes file "kube/allure-docker-service-ui-deployment.yaml" created 
jibl@poste-devops-jbl-16gbram:~/someops/allure-docker-service-ui$ git remote -v
origin  https://github.com/fescobar/allure-docker-service-ui (fetch)
origin  https://github.com/fescobar/allure-docker-service-ui (push)
jibl@poste-devops-jbl-16gbram:~/someops/allure-docker-service-ui$

Ok, but instead of the docker-compose-dev.yaml, I need the docker ui to be defined from an already docker built and pushed image qa.gravitee.io for kubernetes external dns there gonna be a peristent volume claim with map to /app/projects => Where to store the allure reports

maybe an S3 Kubernetes CSI plugin (Container Storage Interface) to get the persistent volume required by the allure service there

=> then for the S3 storage, we havev the target to persist test data from pipelines