When jenkins decides to include or exclude a ref based on the user configured criteria, it should mention this explicitly in the log. This will help a user track down why a job is or is not being launched.
Originally reported by ndimiduk, imported from: Repository scan log should mention when a branch or tag are omitted due to include/exclude filter criteria
- status: Open
- priority: Minor
- component(s): scm-api-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251223-222157
Raw content of original issue
When jenkins decides to include or exclude a ref based on the user configured criteria, it should mention this explicitly in the log. This will help a user track down why a job is or is not being launched.
When jenkins decides to include or exclude a ref based on the user configured criteria, it should mention this explicitly in the log. This will help a user track down why a job is or is not being launched.
Originally reported by ndimiduk, imported from: Repository scan log should mention when a branch or tag are omitted due to include/exclude filter criteria
Raw content of original issue