Search before asking
Use case
As a DevOps engineer I want to fetch the authoritative GitHub Actions job queued timestamp using the REST endpoint GET /repos/{owner}/{repo}/actions/jobs/{job_id}, persist it into the jobs table, and compute queued_duration_sec so platform dashboards and alerts can show job queue time and detect CI queue bottlenecks.
Description
Summary
Add an optional REST-based job collector that calls GET /repos/{owner}/{repo}/actions/jobs/{job_id} for each job discovered and persists jobs[].created_at so job queue time (queued = started_at - created_at) can be computed and aggregated into cicd_pipelines.queued_duration_sec.
Background / problem
- The existing GraphQL-based CollectJobs data (CheckRun) provides startedAt and completedAt but does not reliably expose a job created_at (queued) timestamp.
- Without created_at we cannot compute job queue durations
Proposal
- Implement a new, opt-in REST collector subtask that:
- Uses the job's stable ID (GraphQL DatabaseId / numeric job id) and calls GET /repos/{owner}/{repo}/actions/jobs/{job_id} to retrieve created_at.
- Persists the timestamp to a new column (e.g., job_created_at) on _tool_github_jobs (or to a raw table and then transform/upsert).
- Updates transform/aggregator logic to compute job_queued_sec per job and then aggregate (e.g., average) into cicd_pipelines.queued_duration_sec.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
As a DevOps engineer I want to fetch the authoritative GitHub Actions job queued timestamp using the REST endpoint GET /repos/{owner}/{repo}/actions/jobs/{job_id}, persist it into the jobs table, and compute queued_duration_sec so platform dashboards and alerts can show job queue time and detect CI queue bottlenecks.
Description
Summary
Add an optional REST-based job collector that calls GET /repos/{owner}/{repo}/actions/jobs/{job_id} for each job discovered and persists jobs[].created_at so job queue time (queued = started_at - created_at) can be computed and aggregated into cicd_pipelines.queued_duration_sec.
Background / problem
Proposal
Related issues
No response
Are you willing to submit a PR?
Code of Conduct