You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "JDanP (via GitHub)" <gi...@apache.org> on 2025/10/21 23:52:50 UTC
[I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
JDanP opened a new issue, #8619:
URL: https://github.com/apache/incubator-devlake/issues/8619
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues.
### What happened
Hi! I have a repository in GitLab which my team use with 2 git branches at least. They merge on branch "develop" from feature branches with a merge request. Then they always create another merge request to merge changes from branch "develop" into "main". Every time they merge into "main" it is deployed a new npm version of repository as a library with a job, and then with another automatic job it is bumped up the number of the version in the "package.json" file on branch "develop" so next time "develop" it is merged in "main", "main" can use this new version to publish itself in npm. And it goes like that. Now, the problem I can not understand in DORA metrics is that when I see the "Lead time for changes metrics" I see MRs merged in "develop".
<img width="1380" height="970" alt="Image" src="https://github.com/user-attachments/assets/c2cd9cba-67f6-4751-82bf-7c769bd59b1d" />
### What do you expect to happen
It is supossed that the metrics shows only MRs set up in the rule of the Scope config. In that Scope config I set the name of the job that runs only in "main". It is called: "Publish NodeJs". But it does not respect the config
### How to reproduce
I don´t know
### Anything else
_No response_
### Version
v1.0.2@41c047d
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
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-unsubscribe@devlake.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8619:
URL: https://github.com/apache/incubator-devlake/issues/8619#issuecomment-3688275419
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.
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #8619:
URL: https://github.com/apache/incubator-devlake/issues/8619#issuecomment-3429965164
<!-- Greeting -->
Hi @JDanP! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the incubator-devlake team.
<!-- Answer -->
Your scope config for GitLab CI/CD in DevLake v1.0.2 is designed to filter deployments by job name or branch using regex patterns, but the backend logic actually marks deployments as "production" mainly by matching the environment name against the `EnvNamePattern` regex in the scope config. If your production deployments are identified only by job or branch name (like "Publish NodeJs" on "main"), but the environment name doesn't match your `EnvNamePattern`, DevLake may incorrectly include deployments from other branches (like "develop") in DORA metrics such as Lead Time for Changes. This is a known limitation in v1.0.2—your configuration needs to ensure that the environment name for production deployments matches the pattern you set, or unwanted deployments may be counted. For more details, see the relevant [code logic](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/plugins/gitlab/tasks/deployment_convertor.go) and [documentatio
n](https://github.com/apache/incubator-devlake-website/blob/e88045fa07c85f566017ad361cca987fb292de84/versioned_docs/version-v1.0/Configuration/GitLab.md).
If you want to filter strictly by job name and branch, double-check that your environment naming in GitLab matches your scope config's production pattern. Otherwise, DevLake may not respect your intended filtering.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9c554ed7-56bc-4f98-bf16-4d188626b20a?feedback_type=other)</sup> [](https://app.dosu.dev/b4e8e847-d479-4541-83a8-d88d83fea5c9/ask?utm_source=githu
b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/incubator-devlake/issues/8619)
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
Posted by "klesh (via GitHub)" <gi...@apache.org>.
klesh commented on issue #8619:
URL: https://github.com/apache/incubator-devlake/issues/8619#issuecomment-3441303706
What are the merge options for all merge operations? merge, rebase, or squash?
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8619:
URL: https://github.com/apache/incubator-devlake/issues/8619#issuecomment-3700919091
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.
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug][GitLab CICD Transformations] - Scope Config of a project configuration [incubator-devlake]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #8619: [Bug][GitLab CICD Transformations] - Scope Config of a project configuration
URL: https://github.com/apache/incubator-devlake/issues/8619
--
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-unsubscribe@devlake.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org