|
||||||||
|
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 created a label called 'slaves', which includes QA1 and QA2, but I've set the job to run on QA1, not on 'slaves'. I alse tried deleting the label 'slaves' and explicitly restricting the job to run on QA1. No luck :|
Another weird scenario I've noticed happens before running the tests. I've set up the job to clone or pull the changes from GitHub in a Windows Batch Command script. The workspace is created/updated on QA1 (I can see the changes), but then the browser where the tests are running is launched on QA2.