🐛 Bug Report: 1.27 GitLab discovery regression when using fallbackBranch other than master #24825
Closed
2 tasks done
Labels
area:catalog
Related to the Catalog Project Area
bug
Something isn't working
help wanted
Help/Contributions wanted from community members
📜 Description
Since Backstage 1.27, gitlab discovery is failing to find multiple projects during discovery.
The following configuration in Backstage 1.26 will find GitLab projects that have their default branch set to 'develop'. The same configuration using Backstage 1.27 will only find projects that have a
catalog-info.yaml
file in the same repository as is set byfallbackBranch
The regression is introduced in a70377d where
in
plugins/catalog-backend-module-gitlab/src/providers/GitlabDiscoveryEntityProvider.ts
was changed toHere,
customFallbackBranch
takes precedence over the default branch set in GitLab on project level.👍 Expected behavior
Find all GitLab projects where a catalog-info.yaml file exists in the default branch of that repository
👎 Actual Behavior with Screenshots
👟 Reproduction steps
Using an on-prem GitLab, configure multiple repositories with different default branches. In addition, configure backstage so that
fallbackBranch
is set to another value thanmaster
, e.g.main
📃 Provide the context for the Bug.
On-prem GitLab instance
🖥️ Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: