|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I have a problem using the following situation.
I use a jenkins master and some virtual machines as slaves to start parallel tests.
The virtual machines are configured to use a special test environment (database, WAS, JDK) in every vm.
The test uses a matrix configuration to manage the different test configuration.
At the start of the test every slave VM is resetted to a defined snapshot, to make sure the test conditions are always equal.
After booting the VM, the build, selected for testing is installed on the jenkins slave VMs.
If the Matrix jobs are started on a slave, the testresult is always failure due to the reset to the snapshot of the slave VM and the resultng network error.
So I need the possibility to make sure, all the matrix jobs are started on jenkins master.