TEST-INFRA: [ci-execution-time] Unable to analyze CI execution times due to missing data in Forgejo API #2308

Open
opened 2026-04-03 13:44:48 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: task/ci-execution-time-forgejo-api-data
  • Commit Message: chore(ci): expose and track CI execution time data via reporting mechanism
  • Milestone: v3.8.0
  • Parent Epic: #1678

Background and Context

During a routine analysis of the test infrastructure, it was discovered that the Forgejo API does not currently expose the necessary data to monitor and analyze CI execution times. Specifically, the API responses for pull requests do not contain information about the status, duration, or logs of the associated CI/CD check runs.

This limitation prevents us from identifying performance bottlenecks in the CI pipeline, such as slow-running test suites or inefficient setup steps. Without this data, we cannot proactively optimize the CI process to reduce wait times for developers and ensure a fast feedback loop.

Current Behavior

The Forgejo API responses for pull requests do not include CI check run duration, status, or log data. There is no existing mechanism to track or visualize CI execution time trends over time.

Expected Behavior

CI execution times should be accessible via the Forgejo API or an alternative reporting mechanism. It should be possible to identify the slowest parts of the CI pipeline and monitor performance trends over time.

Acceptance Criteria

  • CI execution times are accessible via the Forgejo API or another reporting mechanism.
  • It is possible to identify the slowest parts of the CI pipeline.
  • A plan is in place for ongoing monitoring and optimization of CI performance.

Subtasks

  • Investigate methods for exposing CI execution data through the Forgejo API or alternative tooling.
  • Configure the CI/CD pipeline to publish test reports with execution times.
  • Implement a mechanism to track and visualize CI performance over time.
  • Update features/ci_workflow_validation.feature to assert execution time reporting is present.
  • Verify all nox stages pass after changes.
  • Confirm coverage ≥ 97% via nox -s coverage_report.

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • CI execution times are accessible via the Forgejo API or another reporting mechanism.
  • It is possible to identify the slowest parts of the CI pipeline.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass.
  • Coverage >= 97%.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `task/ci-execution-time-forgejo-api-data` - **Commit Message**: `chore(ci): expose and track CI execution time data via reporting mechanism` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context During a routine analysis of the test infrastructure, it was discovered that the Forgejo API does not currently expose the necessary data to monitor and analyze CI execution times. Specifically, the API responses for pull requests do not contain information about the status, duration, or logs of the associated CI/CD check runs. This limitation prevents us from identifying performance bottlenecks in the CI pipeline, such as slow-running test suites or inefficient setup steps. Without this data, we cannot proactively optimize the CI process to reduce wait times for developers and ensure a fast feedback loop. ## Current Behavior The Forgejo API responses for pull requests do not include CI check run duration, status, or log data. There is no existing mechanism to track or visualize CI execution time trends over time. ## Expected Behavior CI execution times should be accessible via the Forgejo API or an alternative reporting mechanism. It should be possible to identify the slowest parts of the CI pipeline and monitor performance trends over time. ## Acceptance Criteria - [ ] CI execution times are accessible via the Forgejo API or another reporting mechanism. - [ ] It is possible to identify the slowest parts of the CI pipeline. - [ ] A plan is in place for ongoing monitoring and optimization of CI performance. ## Subtasks - [ ] Investigate methods for exposing CI execution data through the Forgejo API or alternative tooling. - [ ] Configure the CI/CD pipeline to publish test reports with execution times. - [ ] Implement a mechanism to track and visualize CI performance over time. - [ ] Update `features/ci_workflow_validation.feature` to assert execution time reporting is present. - [ ] Verify all nox stages pass after changes. - [ ] Confirm coverage ≥ 97% via `nox -s coverage_report`. ## Definition of Done This issue is complete when: - [ ] All subtasks above are completed and checked off. - [ ] CI execution times are accessible via the Forgejo API or another reporting mechanism. - [ ] It is possible to identify the slowest parts of the CI pipeline. - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - [ ] All nox stages pass. - [ ] Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-03 13:44:57 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#2308
No description provided.