[Bug][gitlab] Deployment count is wrong when downstream pipeline is used

[MarcViola]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Requested this feature to be supported #8009
After testing with downstream pipeline, the number of deployments don't add up.
I've tested a few similar projects and the count is not correct.

What do you expect to happen

It should only be 1 deployment.

How to reproduce

Parent Test:
stage: build
trigger:
include: trigger-child.yml

Child Test:
tags:
- argo-ocp
stage: test
script:
- echo "Child pipeline"
environment:
name: PRODUCTION

Anything else

No response

Version

v1.0.2-beta2@2cadbf8

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

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!

I found a similar closed issue that might be relevant to your problem: How to avoid skipped jobs counting as successful production deployment?. This issue was resolved by a pull request that addressed how skipped jobs were being counted, which might provide insights into handling deployment counts ^[1].

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 ^[2].

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 ^[3].

To continue talking to Dosu, mention @dosu.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.