Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48776

Not able to trigger builds

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: branch-api-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.99
      Bitbucket Branch Source Plugin 2.2.8
      Branch-API-Plugin 2.0.17
    • Similar Issues:

      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, 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?

        Attachments

          Activity

          Hide
          mfoley 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. 

           

          Show
          mfoley 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.   
          Hide
          kgiloo 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

          Show
          kgiloo 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
          Hide
          kgiloo kgiloo added a comment -

          any update on this one?

          Show
          kgiloo kgiloo added a comment - any update on this one?
          Hide
          kgiloo kgiloo added a comment -

          Mike Foley how did you deal with this issue?

          Show
          kgiloo kgiloo added a comment - Mike Foley how did you deal with this issue?
          Hide
          mfoley 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?

          Show
          mfoley 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?
          Hide
          kgiloo kgiloo added a comment -

          Mike Foley : 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.

          Show
          kgiloo kgiloo added a comment - Mike Foley : 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.
          Hide
          jtsievert Jason Sievert added a comment -

          Jenkins 2.107.3, Bitbucket Branch Source Plugin 2.2.11, Pipeline multibranch 2.19 and branch api plugin 2.0.20 are doing the same thing for me.  No mater what I set my Bitbucket team to the downstream multibranchs are stuck at 1 day with no way to change them. 

          Show
          jtsievert Jason Sievert added a comment - Jenkins 2.107.3, Bitbucket Branch Source Plugin 2.2.11, Pipeline multibranch 2.19 and branch api plugin 2.0.20 are doing the same thing for me.  No mater what I set my Bitbucket team to the downstream multibranchs are stuck at 1 day with no way to change them. 

            People

            • Assignee:
              Unassigned
              Reporter:
              mfoley Mike Foley
            • Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: