-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.99
Bitbucket Branch Source Plugin 2.2.8
Branch-API-Plugin 2.0.17
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?
[JENKINS-48776] Not able to trigger builds
Component/s | New: branch-api-plugin [ 18621 ] | |
Component/s | Original: bitbucket-branch-source-plugin [ 21428 ] | |
Environment |
Original:
Jenkins 2.99 Bitbucket Branch Source Plugin 2.2.8 |
New:
Jenkins 2.99 Bitbucket Branch Source Plugin 2.2.8 Branch-API-Plugin 2.0.17 |
Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
I've updated the ticket to reflect that the issue is actually with the Branch-API-Plugin that was updated yesterday (Jan 2, 2018) to 2.0.17. If I revert this back to 2.0.16, the scans to the organization folder will detect changes in the underlying repo(s) and trigger builds.
I've also lower the Priority on this now that I have a workaround.