On Thu, 2018-05-03 at 15:38 +0200, Sébastien Hinderer wrote:
> . . .
>
> So just to make sure we are talking about the same thing, that means
> checking the "None" radio button in the souce code managemnet area,
> then
> check the "run builds remotely (from scripts)" checkbox and then,
> finally, in the commands used to build, clone all the required
> repositories.
I have a bit of a different situation, where I want to use a common
Jenkinsfile across a large number of git repos. Duplicating the
Jenkinsfile everywhere is a very poor solution, so I checkout the
project containing the Jenkinsfile, delete the .git directory in the
WORKSPACE, and then use the scm directives in the Jenkinsfile to
checkout the real project on top. Its far from ideal, but for some
reason it looks like this very common scenario is not supported.
If you have a better way to do this...