Skip to content

Jenkins Jagger Easy Deploy

Jump to bottom
Dmitry Latnikov edited this page Apr 9, 2014 · 37 revisions

jagger easy deploy

This section describes how to deploy Jagger via Jagger Easy Deploy build step.

Choose 'Jagger Easy Deploy' build step.

Jagger Easy Deploy build step

After that you can see blank build step view.

Define Jagger Options

jagger options

Specify Jagger Test Suite

jagger test suit

Determine path to zip file of Jagger Test Suite.

Specify Environment Properties

environment properties

Determine path to properties file. Jagger Nodes MASTER, KERNEL, COORDINATION_SERVER will start with that properties file.

$./start.sh environment.properties

Not filled field means that default properties will be used.

$./start.sh configuration/basic/default.environment.properties

Note! start point to determine path is {JAGGER_HOME} - "runned_jagger"

Additional Environment Properties

additional properties

Additional Environment Properties can be determined. Some configuration properties could be overwritten here.

KEY=VALUE structure

Each property would be added to start command start.sh/start_agent.sh via java option -D :

start.sh environment.properties.file 
-Dchassis.master.session.configuration.bean.name=my_configuration
-Dany.other.property=that.will.pass.to.jagger

Data Base Options

db options false

To use external database

  • check 'Use External Data Base' mark.

  • specify Rdb Client Url, User Name, User Password

db options true

Actually Rdb Driver, Rdb Dialect could be changed.

Unchecked mark means that H2 database will be deployed on Master Node.

Master Node

Necessarily exist in configuration.

master blank

Master Node - Jagger Node with MASTER, COORDINATION_SERVER, HTTP_COORDINATION_SERVER permanent roles.

If external data base is not pointed, RDB_SERVER role will be added to permanent roles. If no Kernel specified , KERNEL role will be added to permanent roles.

fields:
  • Address - required - address of server where Jagger will deploy.
  • User Name - required - name of user that uses in ssh connection.
  • Ssh Key Path - key path that uses in ssh connection via '-i' option. If this field is not defined ssh command will execute without '-i' option.
  • Java Options - options of jvm that starts Jagger. (Change default heap size for example).
  • Set JAVA_HOME - JAVA_HOME can be defined for launching Jagger.

Master filled

Kernel

Optional.

kernel add

Kernel - Jagger Node with KERNEL role

To add KERNEL just click Add in 'Kernels' section.

Kernel has the same options as Master.

kernel blank

To delete current Kernel Delete button presented.

Agent

Optional.

agent add

To add AGENT just click Add button in 'Agent installation' section.

Agent has the same options as Master pluss additional Use JMX option.

agent blank

  • Use JMX option enables to monitor jmx services. Define ports splitted with comas that should be monitored on concrete server.

jmx

To delete current Agent Delete button presented.

Information

Environment properties of jenkins can be used. For example :

  • example 1

  • example 2

  • example 2

It could be applied to every field.

To use not default ports for

  • H2 database
  • Coordination Server port
  • Http Server on Master

Do not forget to point appropriate properties in Additional Properties.

For instance default http port - 8089. We want to use another 8099. Should be defined

  • chassis.coordination.http.port=8099 in Additional Properties or in Environment Properties file.
  • chassis.coordination.http.url=http://{master-server-address}:8099 in additional properties.

More about configuration properties

How easy deploy plug-in actually works

Clone this wiki locally