CNF-23887: Populate JUnit XML timestamp, hostname, and duration

[sebrandon1]

Summary

• Populate timestamp, hostname, and time attributes on the JUnit XML <testsuite> element — these are standard JUnit attributes expected by CI systems like Prow and Jenkins
• Add Duration field to ScanResults, computed centrally in assembleResults
• Add duration_seconds (float64) to JSON output for human-readable scan timing (time.Duration is suppressed from JSON since it serializes as nanoseconds)

Jira: CNF-23887

Before

<testsuite name="TLSSecurityScan" tests="52" failures="0" time="0">

After

<testsuite name="TLSSecurityScan" tests="52" failures="0" time="1754.187"
           timestamp="2026-05-14T13:59:05-05:00" hostname="bpalm-mac">

JSON output (new field)

{
  "timestamp": "2026-05-14T13:59:05-05:00",
  "duration_seconds": 1754.19
}

Test plan

• go build ./... passes
• go test ./... passes
• Live scan against cnfdt16 cluster with --junit-file and --json-file confirms all three attributes populated
• Existing JUnit test updated to assert new fields

[openshift-ci-robot]

@sebrandon1: This pull request references CNF-23887 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Populate timestamp, hostname, and time attributes on the JUnit XML <testsuite> element — these are standard JUnit attributes expected by CI systems like Prow and Jenkins
• Add Duration field to ScanResults, computed centrally in assembleResults
• Add duration_seconds (float64) to JSON output for human-readable scan timing (time.Duration is suppressed from JSON since it serializes as nanoseconds)

Jira: CNF-23887

Before

<testsuite name="TLSSecurityScan" tests="52" failures="0" time="0">

After

<testsuite name="TLSSecurityScan" tests="52" failures="0" time="1754.187"
          timestamp="2026-05-14T13:59:05-05:00" hostname="bpalm-mac">

JSON output (new field)

{
 "timestamp": "2026-05-14T13:59:05-05:00",
 "duration_seconds": 1754.19
}

Test plan

• go build ./... passes
• go test ./... passes
• Live scan against cnfdt16 cluster with --junit-file and --json-file confirms all three attributes populated
• Existing JUnit test updated to assert new fields

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[sebrandon1]

/retest

[richardsonnick]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebrandon1
Once this PR has been reviewed and has the lgtm label, please ask for approval from richardsonnick. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[richardsonnick]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@sebrandon1: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.