• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • branch-api-plugin
    • 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

          Mike Foley created issue -
          Mike Foley made changes -
          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
          Mike Foley made changes -
          Priority Original: Critical [ 2 ] New: Major [ 3 ]

          Mike Foley added a comment -

          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. 

           

          Mike Foley added a comment - 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.   

          kgiloo added a comment - - edited

          Note: there is a dependency of the 

          Pipeline Multibranch plugin 2.17

          to Branch-API-Plugin 2.0.17

          consequently Pipeline Multibranch plugin* *has to be rolled back to 2.16 as well

          this is a serious regression

          kgiloo added a comment - - edited Note: there is a dependency of the  Pipeline Multibranch plugi n 2.17 to Branch-API-Plugin 2.0.17 consequently Pipeline Multibranch plugin * *has to be rolled back to 2.16 as well this is a serious regression
          kgiloo made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          kgiloo added a comment -

          any update on this one?

          kgiloo added a comment - any update on this one?

          kgiloo added a comment -

          mfoley how did you deal with this issue?

          kgiloo added a comment - mfoley how did you deal with this issue?

          Mike Foley added a comment -

          kgiloo - This appears to have been fixed in 2.0.18.  I just checked and that is the version we are currently on and see that it is set to scan every 30 minutes.  I think the other issue with Bitbucket Webhooks was also addressed, so everything seems to be working for us.  Can you check on your end?

          Mike Foley added a comment - kgiloo - This appears to have been fixed in 2.0.18.  I just checked and that is the version we are currently on and see that it is set to scan every 30 minutes.  I think the other issue with Bitbucket Webhooks was also addressed, so everything seems to be working for us.  Can you check on your end?

          kgiloo added a comment -

          mfoley : tested with Pipeline multibranch 2.19 and branch api plugin 2.0.20.

          it seems to work OKAY, but i had to reconfigure my job as "Multibranch pipeline" instead of "Bitbucket Team/project".

          The latter won't be scanned by jenkins at all.

          kgiloo added a comment - mfoley : tested with Pipeline multibranch 2.19 and branch api plugin 2.0.20. it seems to work OKAY, but i had to reconfigure my job as "Multibranch pipeline" instead of "Bitbucket Team/project". The latter won't be scanned by jenkins at all.

            Unassigned Unassigned
            mfoley Mike Foley
            Votes:
            6 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: