We are using Jenkins as our CI system. Currently there is only one master server , with slaves provisioned from open-stack using puppet and foreman for configuration management. If for some reason our Jenkins master goes down , or gets deleted , or something like that , we need to provision a new machine and pull Jenkins master configuration from puppet ( plus copying Jenkins home directory from backup ) , the whole process needs more than one hour. Is there any high availability setup for Jenkins master , active/active or active/passive? so that if one master goes down , the second one will automatically takeover without disturbing any build jobs.?
Did you see the gearman plugin? that permits to have more than one master. It is a kind of HA.
ya , gearman has its own problems , plus what ll happen if gearman server goes down for some reason , so we need HA for gearman also? i am looking for something that is integrated inside Jenkins , plus the two or more masters have the same view of jobs and slave nodes.
- Badges
- Science topic