Background

Our current Data Router task integration with Report Portal provides a solid foundation for test result tracking, successfully sending component metadata, environment details, and tool information. This has enabled valuable insights into our test execution patterns.   We can enhance our Report Portal integration by adding event type and pipeline name context. This will enable new filtering capabilities, particularly for tracking component test health after main branch merges.

Acceptance Criteria

• event_type tag appears in Report Portal for all component test runs
• pipeline_name tag appears in Report Portal for all component test runs
• tags are correctly populated based on the triggering event (push vs pull_request)
• existing functionality remains unchanged

Tags appear in the top right of a report portal run
https://reportportal-smqe.apps.dno.ocp-hub.prod.psi.redhat.com/ui/#subscription_watch/launches/all/347032 

After looking at the datarouter README, it looks like the changes might just be:

• Adding EVENT_TYPE and PIPELINE_NAME parameters to the pipeline specification
• Extending the Data Router task to accept and process these new parameters
• Adding dynamic placeholder replacement in the datarouter.json configuration
• Updating the PipelineRun to pass the appropriate event type and pipeline name values

This approach would build on the existing Data Router task's parameter handling capabilities and follows the same pattern we already established for the SERVICE parameter.

See attached event-type-enhancement.patchfile for the possible implementation details with TODO comments.