Jenkins: Publish Over SSH to multiple hosts without copy/paste

Jenkinsjmeter

I'm using Jenkins' Publish Over SSH Plugin to transfer the same set of files to a group of hosts and then run a small script there. Using the "add server" feature however requires me to repeat source files, remote directory and exec command for every additional server.

https://wiki.jenkins.io/display/JENKINS/Publish+Over+SSH+Plugin

What I'm looking for is a way to specify a list of ssh servers for which the plugin should be executed, preferably in parallel, though the number of servers (4-12) is small enough for a sequential flow too.

Some project specific context:

The publish task is to transfer a JMeter server to a number of load generators and start it there
It is part of the "Build Environment" section right now because the actual build is the execution of the JMeter scenario. If it makes more sense to move any of these steps to a different section, I'm open to that.

Thanks in advance for suggestions.

Best Answer

You can also configure an "Execute shell" block and run there something like:

#!/bin/bash
LISTFILE="servers.list"
for server in $(cat $LISTFILE); do 
  pssh -i -p $SESSIONS -O ConnectTimeout=$TIMEOUT -h $LISTFILE "$COMMANDS"
done

pssh is a free parallel ssh client, more information can be found here.

Related Solutions

Ssh – ForwardAgent in Jenkins

I see this question has been unanswered for over a year, but here is how I solved the problem.

What you want to do is make sure that the user that runs jenkins

checks to see if ssh-agent is running (if not, start it)
checks to see if a key is loaded (if not, load one)

Put this in your ~/.bash_profile for the user that runs jenkins of the user that needs to forward agent, to ensure it runs with each new shell:

SSH_ENV="$HOME/.ssh/environment"

function start_agent {
  echo "Initializing new SSH agent..."
  /usr/bin/ssh-agent | sed 's/^echo/#echo/' > "${SSH_ENV}"
  echo succeeded
  chmod 600 "${SSH_ENV}"
  . "${SSH_ENV}" > /dev/null
  ssh-add .ssh/id_rsa
  cat .ssh/id_rsa.pub
}

#Source SSH Settings

if [ -f "${SSH_ENV}" ]
then
  . "${SSH_ENV}" > /dev/null
  ps -ef | grep ${SSH_AGENT_PID} | grep ssh-agent > /dev/null || {
    start_agent;
  }
else
  start_agent;
fi

if [ `ssh-add -l | grep "The agent has no identities." | wc -l` == 1 ]
then
  ssh-add .ssh/id_rsa
  cat .ssh/id_rsa.pub
fi

About 50% of the code here I took from somewhere else but can't remember where to give credit. This should be fairly portable, and its use need not be limited to jenkins it should work in any ssh-agent forwarding situation.

Windows – publish over ssh jenkins

do you have the "exec in pty" check box set in your jenkins job configuration for send over ssh?

Exec the command in a pseudo tty

This will enable the execution of sudo commands that require a tty (and possibly help in other scenarios too.) From the sudoers(5) man page:

requiretty If set, sudo will only run when the user is logged in to a real tty. When this flag is set, sudo can only be run from a login session and not via other means such as cron(8) or cgi-bin scripts. This flag is off by default.

Best Answer

Related Solutions

Ssh – ForwardAgent in Jenkins

Windows – publish over ssh jenkins

Related Topic