Jagger Jenkins Plug in

jagger-jenkins-plugin

You can find the latest version of the plug-in here.

Plugin gives ability to add two build steps to jenkins job:

• Jagger Easy Deploy
• Jagger Session Comparison

Jagger Easy Deploy

Deploys Jagger via ssh to specified servers. Allows to deploy Jagger without scripting (Execute shell build step). Plug-in creates necessary script automatically.

Starting of Jagger and Jagger agents goes via 'start.sh' / 'start_agent.sh' scripts.

Requirements for jagger-servers:

• linux
• ssh server
• java

How to deploy Jagger via Jagger Easy Deploy build step.

How it works actually.

Jagger Session Comparison

During test run Jagger is controlling if session is running without errors and providing status on session end. It is also possible to compare session results with baseline and take decision if results are acceptable. You can read more about decision making

Both session status and decision of comparison are saved in XML file. Jagger Session Comparison step can process XML file and

• Check session status.
• Check comparison decision.

As result it can mark build as Unstable if session status or comparison decision are not OK.

How to use it.

How to get plug-in

We recommend to download latest distribution. Other option will be to build plug-in from source, like described below.

• Checkout Jagger Jenkins Plug-in

• Create your Jagger Plug-in home directory (a directory where code base will be downloaded to) and set it as an active directory:

  cd PLUG_IN_HOME
  

• Checkout code using the following command:

  git clone [email protected]:griddynamics/jagger-jenkins-plugin.git
  

• Building hpi

mvn clean package

• After that check PLUG_IN_HOME/jagger-jenkins-plugin/target/jagger-jenkins-plugin.hpi is available.

Now it can be added as usual jenkins plugin.

for example: simply put .hpi to $JENKINS_HOME/plugins directory. And restart jenkins.