You can write a Jenkinsfile that creates a clone of any git repository
(calling out to Git with sh step for example), hence Jenkinsfiles can be
central for however many repositories you have. No need for 100's of copies
of the same Jenkinsfile in 100's of git repositories. You can create and
Maybe it sounds a bit crazy, but what about using git submodules. The
jenkinsfile logic is outside the target repo's source as your initial
requirement, although my experience with git submodules is not really
something I'd say I enjoyed it... but it might be something to explore if
it helps.
I second this request but not for the reasons given by Mr. John Mellor.
Instead I request this because our team does not know or understand Jenkins
nor the infrastructure available to it, and should not be allowed to make
changes to the jenkins process without devops oversight. Putting the
On Thu, 2018-05-03 at 16:26 +, Mark Waite wrote:
. . .It seems like you're describing a very good use case for a Pipeline shared
library. Each repository and each branch then has a very simple Jenkinsfile
which loads the shared library and calls it. That's the technique used for
Jenkins
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,
Okay, I just saw its deprecated :( ... the page points to Pipeline Plugin
though, do check it out. I don't have experience using that.
On Thu, 3 May 2018 at 11:23 Vivekanand S V wrote:
> I do that using
> https://wiki.jenkins.io/display/JENKINS/Multiple+SCMs+Plugin
>
>
I do that using https://wiki.jenkins.io/display/JENKINS/Multiple+SCMs+Plugin
This plugin should help you.
On Thu, 3 May 2018 at 10:46 Sébastien Hinderer
wrote:
> Dear all,
>
> Say a project has two repositories: one for its source code and one for
> its test suite.
Dear all,
Say a project has two repositories: one for its source code and one for
its test suite.
How would you do CI for such a project?
I mean, I did try to define several repositories but it seems that
Jenkins only clones the most recently modified rather than cloning all
of them