Jenkins multi-instance architecture

[Tomasz Szandała]

Greetings,

 I am try to scale my Jenkins by splitting the jobs into few, smaller Jenkinses.

The reason: I work in a company that tests software on embedded hardware (each device is on slave).

I'd like to have one prime-master, that gets the requests from user, runs pipeline and in pipeline, depends on e.g. node name, it delegates step to other Jenkins, dedicated for this case.

I could do it using scripted pipeline, that send http request, but maybe there is something better...

[Slide]

Why do you want to have it on separate Jenkins instances? It seems like something you could do with a single Jenkins master and multiple agents as you already have.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9a13a4ef-a786-4918-9d5d-5ce7cb0f0c65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tomasz Szandała]

I could, but quantity of slaves growths really fast. 

I have few minor Teams, that are interested only in one, of those "mini-Jenkinses"

And lastly: I have different networks: some devices are in very restricted networks, and it is easier to open one conection between Jenkinses, than many

I just need something, that triggers job on separate Jenkins - already found http-build-trigger plugin,

but I lack solution for returning the remote job's result.

[Sam Beckwith III]

I'm not sure how to accomplish one master delegating work to other masters except through API requests, however if you are looking for a way to manage multiple jenkins clusters easily I understand Fabric8 to be quite good at this--a master per team.

http://fabric8.io/