Table of Contents
Assuming a TOMCAT deployment, these jar files must be placed under TOMCAT/lib as managed dependencies for hpi to work correctly when built from a cloned repo instance. Otherwise these jars must be moved pre-packaging to hpi within TARGET folder.
akka-actor_2.11-2.3.9.jar akka-cluster_2.11-2.3.9.jar akka-remote_2.11-2.3.9.jar hajp-common-1.0.5.jar config-1.2.1.jar netty-3.8.0.Final.jar protobuf-java-2.5.0.jar scala-library-2.11.5.jar slf4j-api-1.7.7.jar
High Availability Jenkins Project is about creating a fail-over capable cluster of Jenkins instances with selective synchronization , monitoring and control capabilities.
Configuration is described below with annotated images. First Jenkins instance to join the cluster becomes Active Master while all others become Hot Standby members.
When a fail-over occurs, a new Active Master is elected from remaining Hot Standby members.
a Vagrant file is provided for testing purposes... it needs Vagrant version > 1.7.0 and VirtualBox of version 4.3 and above. VagrantFile
All that is required for deployment (assuming Vagrant and VirtualBox is installed in the system) is to run the following command at the same folder with Vagrantfile downloaded above
vagrant up
Vagrant installation tutorials:
Tutsplus Tutorial Vagrant Getting Started
##Configuration After launching the Jenkins instance, please click manage jenkins on left corner of screen.
HAJP-Settings button is among other buttons on the right side of the screen.
This setup information is taken to match Vagrant file provided for testing purposes VagrantFile. Other than IP ranges, same configuration steps are applicable for any HAJP installation.
Use the following settings
- 172.17.0.1 as Orchestrator IP
- 172.17.0.2 as Core1 (port 9080)
- 172.17.0.3 as Core2 (port 9081)
- For convenience please use port 2551 for all components.
After the settings are entered, wait for about 10 seconds and reload settings page to see Jenkins Instance 1 becoming Active Master.
After the settings are entered, wait for about 10 seconds and reload settings page to see Jenkins Instance 1 becoming Active Master.
