Add config file class for C++ Conan `conanfile.txt`
What does this MR do and why?
Background
The Repository X-Ray is a tool that searches for dependency manager configuration files (aka "lock files") and then extracts a list of libraries from the content.
In #474306 (comment 2025085630), we decided to migrate the Repository X-Ray functionality into the GitLab Rails monolith. This gives us two main benefits: (i) it will eventually allow us to run the service outside of the CI pipeline, and (ii) we can maintain the parsing logic centrally so that other domains can utilize it.
Base MR
In !162313 (merged), we introduced the ConfigFiles::Base
class where the intention is for each dependency manager config file type to be represented by a child class. The child class contains the parsing logic to extract a list of libraries and their versions from the file content.
This MR
In this MR, we introduce the CppConanTxt
config file class that parses conanfile.txt
.
For references to the existing parsing logic in the Repository X-Ray repo, see:
- https://gitlab.com/gitlab-org/code-creation/repository-x-ray/-/blob/6634564818dffdeac938014a190b0c604b1da6e0/internal/scanner/scanner.go#L399
- https://gitlab.com/gitlab-org/code-creation/repository-x-ray/-/blob/6634564818dffdeac938014a190b0c604b1da6e0/internal/deps/deps.go#L185
Resolves part of #476177 (closed).
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #476177 (closed)
Merge request reports
Activity
changed milestone to %17.4
assigned to @lma-git
mentioned in issue #476177 (closed)
added 220 commits
-
095b70a0...777c72a7 - 219 commits from branch
master
- b9fefbb5 - Add CPP Conan txt config file class
-
095b70a0...777c72a7 - 219 commits from branch
1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer backend @adie.po
(UTC+0, 7 hours ahead of author)
@jarka
(UTC+2, 9 hours ahead of author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Dzmitry (Dima) Meshcharakou
Hi @missy-gitlab! Could you please do the first backend review here? Please send it to any available maintainer if it looks okay to you. Thanks!
added workflowin review label and removed workflowin dev label
requested review from @missy-gitlab
- Resolved by Dzmitry (Dima) Meshcharakou
added pipeline:mr-approved label
added pipelinetier-2 label
requested review from @dmeshcharakou and removed review request for @missy-gitlab
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for bba2fe78expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 128 | 0 | 16 | 0 | 144 | ✅ | | Plan | 74 | 0 | 1 | 0 | 75 | ✅ | | Verify | 44 | 0 | 2 | 0 | 46 | ✅ | | Govern | 72 | 0 | 0 | 0 | 72 | ✅ | | Manage | 1 | 0 | 1 | 0 | 2 | ✅ | | Data Stores | 31 | 0 | 1 | 0 | 32 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Package | 20 | 0 | 12 | 0 | 32 | ✅ | | Secure | 4 | 0 | 0 | 0 | 4 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Fulfillment | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 391 | 0 | 33 | 0 | 424 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-omnibus:
test report for bba2fe78expand test summary
+-------------------------------------------------------------+ | suites summary | +--------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +--------+--------+--------+---------+-------+-------+--------+ | Create | 551 | 0 | 68 | 0 | 619 | ✅ | +--------+--------+--------+---------+-------+-------+--------+ | Total | 551 | 0 | 68 | 0 | 619 | ✅ | +--------+--------+--------+---------+-------+-------+--------+
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
removed pipeline:run-e2e-omnibus-once label
added this merge request to the merge train at position 2
mentioned in commit 6844cb93
added workflowstaging-canary label and removed workflowin review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
mentioned in merge request !166516 (merged)
added releasedpublished label and removed releasedcandidate label