dosubot[bot] commented on issue #8145: URL: https://github.com/apache/incubator-devlake/issues/8145#issuecomment-2414921843
<!-- Greeting --> Hey @MarcViola! I'm here to help you with any bugs, questions, or contributions you have for the project. Let's work together to solve this issue you're facing! <!-- Answer --> I found a similar closed issue that might be relevant to your problem: [How to avoid skipped jobs counting as successful production deployment?](https://github.com/apache/incubator-devlake/issues/5885). This issue was resolved by a pull request that addressed how skipped jobs were being counted, which might provide insights into handling deployment counts <sup>[[1]](https://github.com/apache/incubator-devlake/issues/5885)</sup>. Regarding your specific issue with downstream pipelines in GitLab, the deployment count may be incorrect because tools like GitLab generate more than one deployment for multiple deployments triggered by one pipeline. Apache DevLake considers these deployments as one and uses the last deployment's finished date as the deployment finished date. To fix this, ensure that DevLake is configured to treat multiple deployments from a single pipeline as one. This involves defining `deployment` in the data transformations while configuring the blueprint of a project <sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v1.0/Metrics/DeploymentFrequency.md)</sup>. For more detailed guidance, you can refer to the transformation rules section in the documentation, which explains how to set up these configurations using regular expressions to identify deployments and production deployments <sup>[[3]](https://github.com/apache/incubator-devlake-website/blob/main/docs/Configuration/GitLab.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- 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
