Hi Martin Henschke ,
many thanks for asking us before starting development on this topic. Awesome!
I'll try to provide you short answers. Please don't hesitate do ask further questions.
- 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?
We have the Jenkinsfile in the root of each repository. So we don't expect the Jenkins plugin to find it anywhere.
- 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?
We do would like to have the posiibility to exclude a repository. So within a project we expext per default every repository containing a Jenkinsfile on root level to be matched, but we would like to be able to exclude specific ones (ideally "configured" inside of the Jenkinsfile or repository).
- What config do you want to be automatically set on each project? How much would need to be individualized for each project?
In this issue we expected to create a Jenkins project with your plugin for each Bitbucket project. So, if you consider providing a "scan" not (only) on Bitbucket project level but on Bitbucket in general, than we only need to select/include/exclude specific Bitbucket projects, nothing more.
- 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?
Well we don't really understand this question, but we do not (expect to) use other plugins beside the "standard" plugins. (Of course we need to be able to configure stuff currently configureable like "Bitbucket Server instance", "Clone from" or the "Behaviours" on the top level.
- 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?
We would be using it "for automatically handling job creation on an ongoing basis".
Many thanks in advance for considering and hopefully takling this issue/feature. If you need any further information, let us know.