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

Automatically Scan Bitbucket Server Project for Repositories

      Hi,

      this plugin creates reliable Webhooks in the repositories hosted in a Bitbucket Server Instance, but one has to manually create at least a multibranch project for this to work. However, it would be nice, if there were an option for an automatic scan for each Repo in a Project, like in the old Plugin from CloudBee (which does not create a Webhook reliable (only like once in ~40 retrys) and also searches a new Maintainer, so I wouldn't bet on this horse anymore).

          [JENKINS-61431] Automatically Scan Bitbucket Server Project for Repositories

          Pat Bee added a comment -

          mhenschke_atlassian
          Answering each of your questions for the environment I'm currently working in.

          • We have the jenkinsfile in the root of the repo.  (I will note that the other plug in allows you to specify the name and path to the jenkinsfile that you want.)
          • If we don't want a repo to match we tend to rename the jenkinsfile or put it in a subdirectory.  (Ex. "jenkinsfile.xx" )
          • In our application the most common alternate configuration is how often to run the build if not triggered.  Some repos are built daily even if there are no commits.
          • We use ALOT of plugins, but in the context of your question I'm not really sure what is in play at that level.
          • We have 272 projects and 4070 repositories, this is really to allow use to not have to manually set up thousands of repos. Or to avoid having to write some sort of code to automate the set up of all of the repositories.

          Pat Bee added a comment - mhenschke_atlassian Answering each of your questions for the environment I'm currently working in. We have the jenkinsfile in the root of the repo.  (I will note that the other plug in allows you to specify the name and path to the jenkinsfile that you want.) If we don't want a repo to match we tend to rename the jenkinsfile or put it in a subdirectory.  (Ex. "jenkinsfile.xx" ) In our application the most common alternate configuration is how often to run the build if not triggered.  Some repos are built daily even if there are no commits. We use ALOT of plugins, but in the context of your question I'm not really sure what is in play at that level. We have 272 projects and 4070 repositories, this is really to allow use to not have to manually set up thousands of repos. Or to avoid having to write some sort of code to automate the set up of all of the repositories.

          Kevin Huber added a comment -

          Hey mhenschke_atlassian,
          why don't you just adopt https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ ?
          The plugin looks for a new maintainer and is widely used.
          All the problems you are trying to solve, are already solved by this plugin.

          Kevin Huber added a comment - Hey mhenschke_atlassian , why don't you just adopt https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ ? The plugin looks for a new maintainer and is widely used. All the problems you are trying to solve, are already solved by this plugin.

          If you extend jenkins.scm.api.SCMNavigator (javadoc), then jenkins.branch.OrganizationFolder (javadoc) can use it. That's how the Bitbucket Branch Source and GitHub Branch Source plugins provide this feature.

          Kalle Niemitalo added a comment - If you extend jenkins.scm.api.SCMNavigator ( javadoc ), then jenkins.branch.OrganizationFolder ( javadoc ) can use it. That's how the Bitbucket Branch Source and GitHub Branch Source plugins provide this feature.

          Pasha Sh. added a comment -

          mhenschke_atlassian Are there any updates around this feature request or maybe a ballpark ETA? Please consider bumping up its priority since it's been pushing users to chose unmaintained cloudbees-bitbucket-branch-source.

          Pasha Sh. added a comment - mhenschke_atlassian  Are there any updates around this feature request or maybe a ballpark ETA? Please consider bumping up its priority since it's been pushing users to chose unmaintained  cloudbees-bitbucket-branch-source.

          Hi pashcan and all the other responders on this ticket, thank you for your comments and sorry I wasn't able to get back to you sooner.

          We've heard your feedback. I can't provide a ballpark ETA at this time, but I hope to target a future release with an implementation of this feature.

          Martin Henschke added a comment - Hi pashcan and all the other responders on this ticket, thank you for your comments and sorry I wasn't able to get back to you sooner. We've heard your feedback. I can't provide a ballpark ETA at this time, but I hope to target a future release with an implementation of this feature.

          Pasha Sh. added a comment -

          Much appreciate your response nonetheless 

          Pasha Sh. added a comment - Much appreciate your response nonetheless 

          Bump, we've had a request for this plugin and aren't able to use it because we need this functionality. Would love to see more features implemented in this plugin as it looks like it has potential to replace multiple other plugins we're using between Jenkins and Bitbucket and it would be great to have a plugin that is supported by Atlassian. Looking forward to an update on the eta!

          Caralee Jackson added a comment - Bump, we've had a request for this plugin and aren't able to use it because we need this functionality. Would love to see more features implemented in this plugin as it looks like it has potential to replace multiple other plugins we're using between Jenkins and Bitbucket and it would be great to have a plugin that is supported by Atlassian. Looking forward to an update on the eta!

          Disappointing that this is still an open issue after years of being open. It's a much needed feature. Ideally we could even scan our entire Bitbucket instance for repositories (i.e. including all projects)

          Jonny van Beek added a comment - Disappointing that this is still an open issue after years of being open. It's a much needed feature. Ideally we could even scan our entire Bitbucket instance for repositories (i.e. including all projects)

          Joe Hewitt added a comment -

          The Cloudbees plugin provides the project level setup for each project (100+ projects) which paired with role matrix plugin allows us to give each team (team = project) self-service capability. From initial setup perspective, we configure the Bitbucket project, Jenkins multi-branch project and permissions for each team when a new project is requested. From that point forward, there is no need for Jenkins administrator to be involved with the teams day-to-day work of adding repos or configuring their build trigger requirements. 

          Without the ability to setup a project that will auto-detect repos/branches, there is a requirement for much more central involvement in regular upkeep of projects in Jenkins. 

          We do have the atlassian-bitbucket-plugin installed to our Jenkins environment as well to take advantage of some of the capabilities is offers like Build integration and rerun from Bitbucket UI. However this becomes confusing as there is overlap in functionality. Once the Atlassian plugin supports project scanning, we can consolidate back down to a single plugin to integrate Bitbucket and Jenkins. 

          Joe Hewitt added a comment - The Cloudbees plugin provides the project level setup for each project (100+ projects) which paired with role matrix plugin allows us to give each team (team = project) self-service capability. From initial setup perspective, we configure the Bitbucket project, Jenkins multi-branch project and permissions for each team when a new project is requested. From that point forward, there is no need for Jenkins administrator to be involved with the teams day-to-day work of adding repos or configuring their build trigger requirements.  Without the ability to setup a project that will auto-detect repos/branches, there is a requirement for much more central involvement in regular upkeep of projects in Jenkins.  We do have the atlassian-bitbucket-plugin installed to our Jenkins environment as well to take advantage of some of the capabilities is offers like Build integration and rerun from Bitbucket UI. However this becomes confusing as there is overlap in functionality. Once the Atlassian plugin supports project scanning, we can consolidate back down to a single plugin to integrate Bitbucket and Jenkins. 

          Jared Kauppila added a comment - I was curious if there will be any movement on this with the `Automate at scale with project-level webhooks` functionality delivered in Bitbucket Data Center 8.8 ?

            mhenschke_atlassian Martin Henschke
            garionion Matthias Detsch
            Votes:
            28 Vote for this issue
            Watchers:
            35 Start watching this issue

              Created:
              Updated: