## Adding role junit2json under playbooks/infra/reporting/roles

### Functionality:

#### 1. Filter plugin `junit2obj`

Converts JUnit to JSON

##### Usage:

```yaml
---
- name: convert junit 2 json
  ansible.builtin.set_fact:
    my_json: "{{ xml_data | junit2obj }}"
```

#### 2. Filter plugin `reportsmerger`

Aggregates N JSON reports into to 1

##### Usage:

```yaml
---
- name: merge files
  ansible.builtin.set_fact:
    my_var: "{{['f1.json', 'f2.json'] | reportsmerger(strategy='normal', output_file='result.json') }}"
```

#### 3. Role `junit2json`

Uses 1. & 2. to convert + merge list of reports

##### Usage:

```yaml
---
- name: convert junit reports to json
  hosts: localhost
  connection: local
  vars:
    junit2_input_reports_list:
      - "/path/to/data/input1.xml"
      - "/path/to/data/input2.xml"
      - "/path/to/data/input2.xml"
    junit2_output_dir: "/path/to/output"
  tasks:
    - name: Apply role junit2json
      ansible.builtin.include_role:
        name: junit2json

```

###### Several control options:

| Variable          | Value   | Resul(t)                             |
| ----------------- | ------- | ------------------------------------ |
| `junit2_do_merge` | `false` | under `junit2_output_dir`            |
| `junit2_do_merge` | `true`  | in `junit2_output_merged_report`     |
| `junit2_out_str`  | `false` | saved as pretty json files           |
| `junit2_out_str`  | `true`  | saved as json strings (with escapes) |

### Tests:

#### Locations

- The tests are under `playbooks/infra/reporting/roles/junit2json/tests/unit`
- The tests data is under `playbooks/infra/reporting/roles/junit2json/tests/unit/data`

#### Running

Running tests from playbooks' folder

```bash
python3 -m pytest ./roles/junit2json/tests/unit
````

### Documentation

To generate role documentation with docsible:

```shell
docsible -r playbooks/infra/reporting/roles/report_send -g -nob -nod
```

Signed-off-by: Maxim Kovgan <makovgan@redhat.com>

Author: mvk

playbooks/infra/reporting/roles/junit2json/README.md

@@ -0,0 +1,16 @@
+# SPDX-License-Identifier: Apache-2.0
+---
+# Default variables for junit2json role
+
+# Custom dummy variables (will be merged with defaults from vars/dummy_variables.yml)
+# Use this to add project-specific template placeholders
+junit2_custom_dummy_variables: {}
+
+# Enable verbose logging for dummy variable processing
+junit2_dummy_debug: false
+
+# Original role defaults (preserved for compatibility)
+junit2_input_merged_report: "merged.junit.xml"
+junit2_output_merged_report: "merged.junit.json"
+junit2_do_merge: true
+junit2_out_str: true

playbooks/infra/reporting/roles/junit2json/defaults/main.yml

@@ -0,0 +1,96 @@
+# Template Handling in junit2json Role
+
+## The Problem
+
+Test data sometimes contains literal strings that look like Jinja2 templates:
+
+```xml
+<testcase name="... expectations failed: {{ expectation_failed }}" />
+<testcase name="... log at: https://ci.example.com/jobs/{{ job_info.job.id }}/states" />
+```
+
+When Ansible processes this data, it tries to evaluate these as templates, causing:
+
+```
+ERROR! 'expectation_failed' is undefined
+ERROR! 'job_info' is undefined
+```
+
+## The Solution
+
+The role provides dummy variables for template patterns. Which method you use depends on **variable frequency** and **your maintenance access**:
+
+## Adding Dummy Variables
+
+### High Frequency Variables (appear across many teams/projects)
+
+**If you maintain the role:**
+Edit `vars/dummy_variables.yml`:
+
+```yaml
+junit2_dummy_variables:
+  # Add variables that many teams encounter
+  common_variable: "PLACEHOLDER_COMMON_VARIABLE"
+  shared_info:
+    build_id: "PLACEHOLDER_BUILD_ID"
+```
+
+**If you don't maintain the role:**
+Request the role maintainer to add these variables to `vars/dummy_variables.yml`.
+
+### Low Frequency Variables (specific to your team/project)
+
+**If you maintain the playbook:**
+Add variables when calling the role:
+
+```yaml
+- name: Convert test reports
+  ansible.builtin.include_role:
+    name: junit2json
+  vars:
+    junit2_custom_dummy_variables:
+      # Add team-specific variables
+      pipeline_id: "PLACEHOLDER_PIPELINE_ID"
+      deployment:
+        environment: "PLACEHOLDER_ENVIRONMENT"
+```
+
+**If you don't maintain the playbook:**
+Create an external variables file `my_extras.yml`:
+
+```yaml
+junit2_custom_dummy_variables:
+  pipeline_id: "PLACEHOLDER_PIPELINE_ID"
+  deployment:
+    environment: "PLACEHOLDER_ENVIRONMENT"
+```
+
+Run with:
+
+```shell
+ansible-playbook my_playbook.yml -e @my_extras.yml
+```
+
+### Debug Mode
+
+Enable debug to see what variables are being set:
+
+```yaml
+junit2_dummy_debug: true
+```
+
+## Role Maintenance & Feedback
+
+**This role is maintained by:** GitHub team `@redhatci/verification`
+
+**Help us improve:** Please share your custom dummy variables with the maintenance team! When you add variables using `junit2_custom_dummy_variables` or external files, let `@redhatci/verification` know what variables you needed. This helps us identify high-frequency variables that should be moved into the role for everyone's benefit.
+
+## Variables Already Handled
+
+These patterns are already handled (may change based on test data encountered):
+
+- `{{ expectation_failed }}`
+- `{{ job_info.job.id }}`
+- `{{ ci_job_id }}`
+- `{{ error_message }}`
+- `{{ timestamp }}`