sobanjom opened a new issue, #8823:
URL: https://github.com/apache/incubator-devlake/issues/8823

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### 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?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to