jenkinsci / jenkinsci/branch-api-plugin
[JENKINS-48776] Not able to trigger builds
- Dominant language
- Java
- Stars
- 39
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
I have configured a Bitbucket (server) team/project in jenkins and specified the "Scan Organization Folder Triggers" to 5 minutes (webhooks are also not working, possibly due to JENKINS-48483">JENKINS-48483, so I am relying on scanning). This will scan the organization folder for any changes, but it's not triggering a scan of the multibranch pipeline so no builds are getting triggered.
When I create the Bitbucket Team/Project, I am able to specify the organizational scan frequency, but when I view the projects's configuration, I see that it is set to 1 day and I can't change it. Is there a way to correct this?
---
Originally reported by mfoley, imported from: Not able to trigger builds
Raw content of original issue
I have configured a Bitbucket (server) team/project in jenkins and specified the "Scan Organization Folder Triggers" to 5 minutes (webhooks are also not working, possibly due to
JENKINS-48483, so I am relying on scanning). This will scan the organization folder for any changes, but it's not triggering a scan of the multibranch pipeline so no builds are getting triggered.
When I create the Bitbucket Team/Project, I am able to specify the organizational scan frequency, but when I view the projects's configuration, I see that it is set to 1 day and I can't change it. Is there a way to correct this?
environment
```
Jenkins 2.99
Bitbucket Branch Source Plugin 2.2.8
Branch-API-Plugin 2.0.17
```
Contributor guide
Research direction
Start in the branch-api-plugin code paths for organization-folder scan triggers and the Bitbucket team/project configuration, using the reported Jenkins 2.99 and plugin versions to reproduce the behavior. Trace why a configured five-minute scan becomes one day and does not trigger multibranch scans; done means the configured interval is preserved and builds are triggered by the scan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100