Hello,
--> Current Limitations:
Our largest client (500+ users and 3000 applications) faces two key challenges with the current GitLab.queryProject task in Digital.ai Release:
- Ambiguous Project Search:
*The task fails silently when multiple projects match a pattern (e.g., cloud_sample_service*), causing pipeline failures.
*Teams resort to custom scripts to filter out forks or user projects, adding complexity.
- Limited Output Properties:
*Currently, only the project ID is returned in the output properties.
*Useful attributes like http_url_to_repo, name, namespace, and default_branch are not exposed, forcing additional API calls to retrieve them.
-->Proposed Enhancements:
1. Precise Project Search:
Add two new parameters to improve accuracy and reliability:
strictSearch: true – Enforces exact-name matching (e.g., cloud_sample_service ≠ cloud_sample_service_test).
kind: "group" – Filters out user forks (kind: "user").
2. Enrich Output Properties:
Extend the output properties to include additional GitLab project attributes that can be reused in templates:
http_url_to_repo – Direct link to the repository.
name – Project name.
namespace – Project namespace (e.g., group/project).
default_branch – Default branch of the repository.
web_url – URL to the project in GitLab.
ssh_url_to_repo – SSH URL for cloning.
visibility – Project visibility (private/public/internal).
-->Why This Matters:
Precision: Ensures accurate project identification, avoiding silent failures.
Efficiency: Reduces the need for custom scripts and additional API calls.
Flexibility: Provides more context and attributes for use in downstream tasks (e.g., triggering CI pipelines, generating documentation, or configuring deployments).
Alignment with GitOps: Supports best practices by providing all necessary project details in a single call.
--> Impact:
Low Risk: Backward-compatible; existing behavior is preserved by default.
High Value: Addresses critical pain points for large teams using GitLab CI with Digital.ai Release.
Regards,
by: Mahdi S. | 8 days ago | Integrations

Comments