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

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When investigating into the CI/CD schema, I found that
   - table cicd_pipelines lacks the field `started_date`
   - table cicd_tasks lacks the field `created_date`
   
   These two fields are different in CI/CD workflows. For instance, if a GitLab 
job is queued after it's created, its `created_date` and `started_date` will be 
different.
   
   
![image](https://github.com/apache/incubator-devlake/assets/14050754/929c7dcb-8d5f-43a7-b491-70f18e58c055)
   
   
   ### What do you expect to happen
   
   - [ ] Add the field `started_date`to table cicd_pipelines
   - [ ] Add the field `created_date`to table cicd_tasks
   - [ ] Check the (tool to domain layer) transformation logic of 
`created_date` and `started_date` in cicd_pipelines
      - [ ] GitLab
      - [ ] Bamboo
      - [ ] GitHub 
      - [ ] Jenkins
      - [ ] BitBucket
      - [ ] Azure
   - [ ] Check the (tool to domain layer) transformation logic of 
`created_date` and `started_date` in cicd_tasks
      - [ ] GitLab
      - [ ] Bamboo
      - [ ] GitHub 
      - [ ] Jenkins
      - [ ] BitBucket
      - [ ] Azure
   
   ### How to reproduce
   
   Collect a GitLab job that has been queued.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   main
   
   ### Are you willing to submit 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