From Ibutsu report is not possible to infer the original MR/PR that triggered it.

We should enrich Ibutsu metadata to link test report to MR/PR.

This would be used as filter, giving us an overview of test runs of a particular MR/PR directly from Ibutsu.

We can leverage the --ibutsu-source argument and set it to MR/PR through CI environment variables.

To do so, during bonfire deploy-iqe-cji the environment variable IQE_IBUTSU_SOURCE can be set to something like "SMOKE-${CI_MERGE_REQUEST_PROJECT_ID}MR${CI_MERGE_REQUEST_IID}" (ref.).

Then by using the following URL (customized ad-hoc) we can query every run for a particular plugin https://ibutsu.insights.corp.redhat.com/project/3915c900-85fc-1222-833c-10d51af56f2e/runs/?page=1&pageSize=20&source=%5Bregex%5DSMOKE-.*swatch.*mr.* This can also be printed in the after_script step of the pipeline. In that place we can leverage CI_MERGE_REQUEST_IID to pinpoint the current run's Ibutsu report.

Note that the project ID (3915c900-85fc-1222-833c-10d51af56f2e) must be hard coded (as GitLab CI variable) because the actual Ibutsu reporting is done though a not observable dependency.

Acceptance criteria:

• Every Ibutsu report generated by a pipeline run in a MR/PR have the "source" value pointing to the MR/PR of origin.
• There is a reference to the query in smoke test logs.