nicolavolpini commented on issue #7193: URL: https://github.com/apache/incubator-devlake/issues/7193#issuecomment-2063300502
> I think this would be common to most real-world users, they won't be starting out with devlake in place, they will be adding it to probably quite mature teams with long histories which are incomplete. the system needs to be able to handle picking up from a postiion of only being told about new deployments even though there is a long commit history already. This is precisely the situation we are in. In our case, we had to rely on Webhooks for deployments since our pipeline structure - although it uses Jenkins - makes it impossible to correlate Jenkins deployment SHAs to GitHub PR SHAs (we have an intermediate step where Jenkins is picking artifacts from a central repo, thus a different SHA is shown in the job). On a side note: what I expected was for a deployment webhook to be bound only to the PR it relates to. This is at least what I assumed as a user approaching DevLake and DORA metrics for the first time. I think it's a natural assumption. -- 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]
