Unfortunately I cannot help you with installing Jenkins (though I don't think it's really difficult) because in my case I already had it installed by DevOps people.
But creating a new job that runs your automated tests is not a big deal. Before doing this please check following things:
If you want Jenkins to show fancy graphs with tests results (without this there is probably not much sense in setting up this job) you need to be sure that the tool/framework you use is capable of saving the test results to the XML files with special structure recognised by Jenkins/Hudson. Some of the tools have this support out of the box, for some others you will have to install additional libraries.
To login on the remote server and execute scripts there you need an SSH access to that server and you need to add those credentials to the settings of Jenkins. For this, open '/configure' URL in Jenkins and find 'SSH remote hosts' session. Click 'Add' button to add new credentials and don't forget to save the settings afterwards.
You MIGHT have issues with one machine not capable to login to another via SSH because of missing certificates, so you need to double-check this with your system administrators/DevOps.
After this, do the following:
Hit the 'New item' button on the left side of Jenkins main page
Choose 'New freestyle project'
On the top, enter project name and description
Scroll down and click 'Add build step' button. Select 'Execute shell script on remote host using ssh'. In 'SSH site' drop-down, select your SSH credentials and enter the command in 'Command' field. In my case, I had a bash script which spins up a vagrant machine that checks out the latest test version and runs them against another server. The commands in my case are looking like this:
sshpass -p "password" scp -r /var/acceptance-tests/output 192.168.40.14:$WORKSPACE
With first command I navigate to the folder with bash script, then I run it and with the last command I copy the results in XML to the server where Jenkins is located (unfortunately I don't know better way to do it other than using sshpass util and in this case I need to write a password in plain text).
- Click 'Add post-build action' and choose 'Publish JUnit test result report'. For the example, above 'Test report XMLs' field value would be '\output*.xml'. Check 'Retain long standard output/error' checkbox as well.
That's basically all (in this example I'm not covering additional settings you may change in the job).