+1

This would be a major feature for us and probably many others. We are currently using https://github.com/jenkinsci/bitbucket-branch-source-plugin which has some bugs and is, as stated by Matthias, up for adoption, so we would like to switch to the official plugin by Atlassian. The only feature blocking us right now is this one, scanning Bitbucket-Projects for repositories with Jenkinsfiles and creating Jenkins multi branch pipeline projects for them (like it does now already, but currently only for one specific repo).

+1

+1

+1

I currently have something like when the using the bitbucket-branch-source plugin to create multi-branch for all repos in FOO Bitbucket project. Being able to replicate that with the atlassian-bitbucket-server-integration-plugin would be great.

organizations {
 bitbucket {
   serverUrl("https://bitbucket.example.com:8443")
   repoOwner("FOO")
   credentialsId("bitbucket_password_credential")
   traits {
     bitbucketBranchDiscovery{strategyId(0)}
     bitbucketPullRequestDiscovery{ strategyId(1)}
   }
 }
}

buildStrategies {
 buildRegularBranches()
 buildChangeRequests{ ignoreTargetOnlyChanges(false) ignoreUntrustedChanges(false) } }

projectFactories {
 workflowMultiBranchProjectFactory{ scriptPath 'Jenkinsfile' scriptPath 'debian/Jenkinsfile' }
}

triggers { periodicFolderTrigger{ interval('5m') } }
orphanedItemStrategy { discardOldItems { } }

}

Hi Matthias, and everyone who has commented on this issue- thank you for your input and suggestions! We are investigating an implementation of this at the moment.
For now, we are still exploring what a technical design would look like, but we have a number of questions about the kind of configuration options you will need on such a project. Specifically:

• Do you store your Jenkinsfile in a consistent location for every repository in a project? Would you expect the plugin to be able to "find" your Jenkinsfile anywhere in the project, or would the restriction of a consistent path be appropriate?
• When scanning a project, would you want every repository with a Jenkinsfile to be matched, or just a subset? If so, what kind of criteria would you want to include/exclude repositories?
• What config do you want to be automatically set on each project? How much would need to be individualized for each project?
• Do you rely on many other plugins, apart from the Bitbucket Jenkins Integration plugin in your multibranch projects? If so, do you need/expect this configuration to be carried over to child projects? Which plugins do you use?
• And more generally, would you be using this as a migration tool (so you can quickly generate a lot of Jenkinsfiles), for automatically handling job creation on an ongoing basis, or both?

If you have time to answer these questions, it would be a great help. You can leave comments on this ticket, or by email. Thank you again!