Jenkins Multibranch Pipeline and checkout of subversion

[Kristian]

Hey,

I think there is something odd with Multibranch plugin or I have done
something wrong. I have a repository:

> http://svnserver/some/svn/repo

This repo has a trunk path and some branches like this:

- http://svnserver/some/svn/repo/trunk
- - http://svnserver/some/svn/repo/branch/1.0
- - http://svnserver/some/svn/repo/branch/2.0
and so on

So, in every of these paths, I've added a file names "Jenkinsfile",
where I have something in it like

node('theNodeForTheCurrentBranch') {
checkout ([ $class: 'SubersionSCM' ...
}

Now, I click on "Branch Indexing" -> "Run Now" on this Multibranch
project. Now, this project creates some new jobs according to the
Jenkinsfiles in trunk and the branches, e.g.

-> Multibranch Job Name/trunk
-> Multibranch Job Name/branch/1.0
-> Multibranch Job Name/branch/2.0

Now, when I start one of these jobs, the job first checkouts the svn
repo on the master, then loads the Jenkinsfile, and then checkouts the
svn repo on the node on which the job should checkout.

Is there a way to change the behaviour so the multibranch job checks
out only the Jenkinsfile on the master and not the whole repository?
Or is there something I missunderstood something and therefore did
something wrong?

[Gilad Baruchian]

Did you find any solution for that? I have this problem as well

[Robert Hales]

https://groups.google.com/forum/#!topic/jenkinsci-users/yYeedbtXT4g