thiDucTran commented on issue #5207: URL: https://github.com/apache/incubator-devlake/issues/5207#issuecomment-1958832175
> In my opinion, to use ArgoCD, DevLake needs to make a relationship between deployment repository commit (for manifests) and application repository commit (for source codes). im thinking about the same. one way that i can think of is this flow: 1. CI tool (jenkins, tekton, any CI tool) builds from application and produces a docker image. the same CI tool would create a PR to update deployment repo to update the docker image of manifest(s); when creating the PR ...we can put the commit hash of the app's repo? this is because when ArgoCD deploys the new docker image ..it can parse to get that commit hash and `POST` it to devlake via webhook? -- 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: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
