wouldd commented on issue #7193: URL: https://github.com/apache/incubator-devlake/issues/7193#issuecomment-2014686488
@klesh that certainly sounds plausible. I'm trying to wrap my head around your point 1 about all deployment commits forming a linear history 'newer deployment commit should contain all older deployment commits' I'm not sure I understand why that would be desired? I would assume that for change cycle time you need 1) a deployment id with it's date of deployment, result, environment. 2) a set of commit shas that are linked to that deployment id as the vehichle that deployed them, 3) a lookup of all commits with their commit date and a link to the PR that merged them. So you would process a deployment row, link it's deployment commits and join to their commit records and pr record. then calculate the various time deltas for commit->pr create->pr-merge->deployment to production and record that cycle tyime against those commits. So any commit that has no associated deployment would have no cycle time values (the vast majority of our commit history was deployed long ago and we won't be back porting that information just starting from now) dora calcs /boards would work on only those commits that have non-null values for cycle time I'm not sure I see in this why a deployment commit would be linked to older deployments at all? -- 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]
