-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QE] Reportportal launch for failed pipeline run #4412
Comments
Do we have any example of this error? |
We aim to using reportportal to check all tests as ocp clear pipeline runs in one or two days. But if pipeline failed before task So we need a final task that triggered if the pipeline run failed. This task will collect the failed info and import to reportportal. |
So I plan to upgrade the
@adrianriobo WDYT? |
Yeah so I would suggest a different cause one key issue right now is that when you provision a machine the state used by mapt on our pipelines is stored on the same PVC..so if you delete the content before running the decommission we may end up on situation where machines from mapt will not be detroyed. Also this behavior of using the workspace (PVC) to keep the state and also move the credentials can be changed and actually we should change it (to be in line with best practices). One is to keep the state on s3 and the other is move the info required to connect to the machine from workspace to create secrets holding it. This is ready but not merged here redhat-developer/mapt#336 So with all said I would suggest: Prioritize to move redhat-developer/mapt#336 in as so we will remove the PVC dependency for the state (this will require touch on each pipeline we are currently using) Then you can create simple cleanup task which can be executed in parallel on the final block after the sync of the information has been completed on repor portal and s3 WDYT? |
Cannot find remove-pvc-resource source on crc-qe-virtualized Looks it is applied on openshift cluster and conflicts with decommision task causing machines to not be decommisioned. can we add a condition to be disabled by default? At this moment this only affects to release test, so nightly is not affected |
@albfan |
Upload MR that create a reportportal v1.2.0 |
Currently, if the pipeline run failed before
reportportal-import
task, there is no record of the failure(as pipeline run periodically clean).Add a post task for pipeline run if it's failed. This task will create a XML file that include the failure details and import the xml file to reportportal.
The text was updated successfully, but these errors were encountered: