From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= Slave machines | |description= Slave machines | ||
{{result|fail}} Note this test will probably fail: [https://bugzilla.redhat.com/show_bug.cgi?id=1147978 rhbz#1147978] [https://bugzilla.redhat.com/show_bug.cgi?id=1147831 rhbz#1147831] | |||
|setup= | |setup= |
Latest revision as of 13:38, 30 September 2014
Description
Slave machines
Note this test will probably fail: rhbz#1147978 rhbz#1147831
Setup
- ensure that Jenkins is running
- you will need a virtual machine with SSH access for this test (or another physical machine)
- you can get one easily with virt-builder
- this test case depends on plugins test case
How to test
- go to http://localhost:8080/computer/new
- enter node name: "slave1" and select "Dumb Slave" option
- click OK
- set "Remote root directory" to "/tmp/jenkins"
- this is just for test
- make sure that "Launch method" is set to "Launch slave agents on Unix machines via SSH"
- set "Host" to your VM's hostname/IP
- click "Add" next to "Credentials"
- from "Kind", select "Username with password"
- enter username and password which jenkins can use to access the VM
- click "Add"
- you should be back in slave configuration screen and your credentials should be selected in "credentials" drop-down menu
- click "Save"
- go to http://localhost:8080/computer/slave1/
- note "slave1" in URL is name of the slave, replace it with correct name if needed
- and click "Launch slave agent"
- you should see console output which indicates that slave machine is up and running
- go to http://localhost:8080/computer/slave1/script
- and try to execute command: println "uname -a".execute().text
- click "run"
- you should see the output of "uname -a" executed on slave machine
Expected Results
- user shouldn't encounter any error messages or unexpected stacktraces, everything should work as described