-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
jenkins 2.401.3
gitlab branch source plugin 664.v877fdc293c89
gitlab enterprise edition 15.4.0-ee (self hosted)
we have a gitlab group containing several repos, on our jenkins we define a gitlab organizatinal folder "looking" on that group.
when we add new repos containing Jenkinsfile, and scan the group - the repo appears in jenkins properly.
however, when we delete a repo which already appears in jenkins and rescan the group, the attached exception appears in the scan log. (see attached file, urls changed for security reasons).
we believe this behavior is a bug of a non-handled flow in the plugin.